| 3 |
Approval of the Agenda |
|
| R3-231100 |
RAN3#119bis-e Meeting Agenda |
RAN3 Chair |
| 4 |
Approval of the minutes from previous meetings |
|
| R3-231101 |
RAN3#119 Meeting Report |
ETSI-MCC |
| R3-231936 |
RAN3#119 Meeting Report |
ETSI-MCC |
| 5 |
Documents for immediate consideration |
|
| R3-231181 |
Guidelines for RAN3 Electronic Meetings |
RAN3 Chair, RAN3 Vice-Chairs |
| 6 |
Organizational topics |
|
| R3-231505 |
Handling of LSin |
Huawei |
| 7 |
General, protocol principles and issues |
|
| R3-231102 |
TR 30.531 v1.45.0 Work Plan and Working Procedures - RAN WG3 |
ETSI-MCC |
| 8.1 |
New Incoming LSs |
|
| R3-231104 |
LS on Network Triggered Service Request for a UE in Suspend State |
CT4, Ericsson |
| R3-231108 |
LS on 1-symbol PRS |
RAN1, ZTE |
| R3-231109 |
Reply LS on PDU Set Handling |
RAN2, Chinamobile |
| R3-231121 |
LS on RAN UE Id optionality |
SA5, Ericsson |
| R3-231159 |
LS on Paging Policy Information for Network Triggered Connection Resume |
CT4, Ericsson |
| R3-231160 |
LS on Network Triggered Service Request for a UE in Suspend State |
CT4, Ericsson |
| R3-231161 |
Reply LS on RB set configuration |
RAN1, ZTE |
| R3-231162 |
LS Reply on PRU Procedures |
RAN1, Qualcomm |
| R3-231163 |
LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
RAN1, Fujitsu, CATT |
| R3-231164 |
LS on 1-symbol PRS |
RAN1, ZTE |
| R3-231165 |
Reply LS on PDU Set Handling |
RAN2, Chinamobile |
| R3-231166 |
LS on Continuity of QoE measurements during intra-5GC inter-RAT HO |
RAN2, Huawei |
| R3-231167 |
LS on buffer level threshold-based RVQoE reporting |
RAN2, Apple |
| R3-231168 |
Reply LS on RACH enhancement for R18 SONMDT |
RAN2, Huawei |
| R3-231169 |
LS on INACTIVE eDRX above 10.24sec and SDT |
RAN2, Intel |
| R3-231170 |
Reply LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN |
RAN2, Nokia |
| R3-231171 |
Reply LS on Proposed method for Time Synchronization status reporting to UE(s) |
RAN2, Nokia |
| R3-231172 |
LS on SRS configuration request |
RAN2, Huawei |
| R3-231173 |
LS on the use of PEI during an emergency PDU session |
RAN2, Ericsson |
| R3-231174 |
Reply LS on applicability of timing error margin of Rx TEG |
RAN4, CATT |
| R3-231175 |
LS on Excess Packet Delay Threshold for MDT |
SA5, Nokia |
| R3-231176 |
Reply LS on QoE measurements in RRC IDLE/INACTIVE states |
SA5, Huawei |
| R3-231177 |
LS on RAN UE Id optionality |
SA5, Ericsson |
| R3-231178 |
LS on 3GPP work on Energy Efficiency |
SA5, Huawei |
| R3-231179 |
LS on Approval of eQoE CRs for NR |
SA5, Ericsson |
| R3-231180 |
Reply LS on introduction of a new attribute “Only Resource Coordination” to support source coordination between LTE and NR SA |
SA5, Chinatelecom |
| R3-231251 |
Discussion on LS reply from RAN2 on MRB PDCP topics |
Ericsson |
| R3-231292 |
Reply LS on the use of PEI during an Emergency PDU session |
Nokia, Nokia Shanghai Bell |
| R3-231365 |
Discussion on INACTIVE eDRX above 10.24sec and SDT |
ZTE |
| R3-231622 |
UE identifiers for management-based trace data |
Ericsson |
| R3-231623 |
[DRAFT] Reply LS on RAN UE Id optionality |
Ericsson |
| R3-231632 |
Discussion on LS on RAN UE Id optionality |
Nokia, Nokia Shanghai Bell |
| R3-231633 |
[Draft] Reply LS on RAN UE Id optionality |
Nokia, Nokia Shanghai Bell |
| R3-231698 |
Discussion on RAN UE ID for management-based TRACE and MDT |
ZTE |
| R3-231699 |
RAN UE ID for management-based TRACE and MDT - XnAP |
ZTE |
| R3-231700 |
RAN UE ID for management-based TRACE and MDT - X2AP |
ZTE |
| R3-231701 |
draft reply Discussion on RAN UE ID for management-based TRACE and MDT |
ZTE |
| R3-231723 |
Discussion on trace in CU-DU split and dual connectivity |
Huawei |
| R3-231724 |
[DRAFT] Reply LS on RAN UE Id optionality |
Huawei |
| R3-231835 |
Support 1-symbol PRS [TEI18] |
ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei |
| R3-231836 |
Support 1-symbol PRS [TEI18] |
ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei |
| R3-231837 |
[DRAFT] reply LS for 1-symbol PRS |
ZTE |
| R3-231857 |
CB: # 1_1-symbol_PRS - Summary of email discussion |
ZTE - moderator |
| R3-231858 |
CB: # 2_RANUEID_SA5 - Summary of email discussion |
Ericsson - moderator |
| R3-231933 |
Support 1-symbol PRS [1symbol_PRS] |
ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei |
| R3-231934 |
Support 1-symbol PRS [1symbol_PRS] |
ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Samsung, Huawei |
| R3-231935 |
[DRAFT] reply LS for 1-symbol PRS |
ZTE |
| R3-232161 |
[DRAFT] Reply LS on RAN UE Id optionality |
Ericsson |
| R3-232162 |
[DRAFT] Reply LS on RAN UE Id optionality |
Ericsson |
| 8.2 |
LSin received during the meeting |
|
| R3-232105 |
Reply LS on buffer level threshold-based RVQoE reporting |
SA4 |
| R3-232106 |
Reply LS on 3GPP work on Energy Efficiency |
CT1 |
| R3-232107 |
Reply LS on Tracking IANA assignment requests |
CT4 |
| 8.3 |
Left over LSs / pending actions |
|
| R3-231452 |
Discussion on RAN information exposure for XRM |
Lenovo |
| R3-231496 |
Correction on IP address mapping for IAB topology update |
Huawei |
| R3-231497 |
[draft] Reply LS on F1-C IP addresses mapping during IAB topology update |
Huawei |
| R3-231498 |
Discussion on the RAN information exposure for XRM |
Huawei |
| R3-231499 |
CR on support UP based QoS notification control for XR |
Huawei |
| R3-231500 |
CR on support UP based QoS notification control for XR |
Huawei |
| R3-231501 |
[draft] Reply LS on RAN information exposure for XRM |
Huawei |
| R3-231550 |
Discussion on SA2 LS on RAN information exposure for XRM |
Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231551 |
Reply LS on RAN information exposure for XRM |
Ericsson |
| R3-231560 |
Discussion on RAN information exposure for XRM |
CATT |
| R3-231561 |
Reply LS on RAN information exposure for XRM |
CATT |
| R3-231760 |
Discussion on NR support for UAV |
Huawei |
| R3-231761 |
[draft] Reply LS on RAN dependency for UAS |
Huawei |
| R3-231802 |
Discussion on exposing NG-RAN information |
CMCC |
| R3-231803 |
Draft reply LS on RAN information exposure for XRM |
CMCC |
| R3-231851 |
Discussion on RAN information exposure for XRM |
ZTE |
| R3-231852 |
[DRAFT] Reply LS on RAN information exposure for XRM |
ZTE |
| R3-231853 |
TP to TS 38.413 for RAN information exposure for XRM |
ZTE |
| R3-231854 |
TP to TS 38.415 for RAN information exposure for XRM |
ZTE |
| R3-231859 |
CB: # 3_RANexposure_XRM - Summary of email discussion |
Lenovo - moderator |
| R3-232129 |
Reply LS on RAN information exposure for XRM |
Ericsson (to be RAN3) |
| R3-232169 |
Reply LS on RAN information exposure for XRM |
Ericsson (to be RAN3) |
| 9.1 |
LTE |
|
| R3-231220 |
Correction for SubcarrierSpacingSSB |
Nokia, Nokia Shanghai Bell, Qualcomm, Huawei |
| R3-231909 |
CB: # 47_SubcarrierSpacing SSB |
Nokia |
| R3-232030 |
Correction for SubcarrierSpacingSSB [NR_ext_to_71GHz-Core] |
Nokia, Nokia Shanghai Bell, Qualcomm, Huawei |
| 9.2.1 |
SONMDT |
|
| R3-231190 |
Alignment of the tabular and ASN.1 definitions for the Resource Status Update |
Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung |
| R3-231191 |
Alignment of the tabular and ASN.1 definitions for the Resource Status Update |
Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung |
| R3-231267 |
Correction on Mobility Change procedure |
Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm, ZTE, Orange, Vodafone |
| R3-231268 |
Correction on Mobility Change procedure |
Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm, ZTE, Orange, Vodafone |
| R3-231546 |
Correction on RACH Report IE |
Ericsson |
| R3-231547 |
Correction on RACH Report IE |
Ericsson |
| R3-231548 |
Correction on RACH Report IE |
Ericsson |
| R3-231549 |
Correction on RACH Report IE |
Ericsson |
| R3-231611 |
F1AP Rel-17 correction for NR-U metrics |
Ericsson, Qualcomm Incorporated, Samsung, Nokia, Nokia Shanghai Bell |
| R3-231612 |
XnAP Rel-17 correction for NR-U metrics |
Ericsson, Qualcomm Incorporated, Samsung, Nokia, Nokia Shanghai Bell |
| R3-231685 |
Correction on RESOURCE STATUS FAILURE message over E1 in Rel-16 |
ZTE, China Telecom, CMCC, Lenovo, China Unicom |
| R3-231686 |
Correction on RESOURCE STATUS FAILURE message over E1 in Rel-17 |
ZTE, China Telecom, CMCC, Lenovo, China Unicom |
| R3-231687 |
Correction on Event-based Reporting for Inter-system Resource Status Request |
ZTE, Nokia, Nokia Shanghai Bell, China Telecom, CMCC, Lenovo |
| R3-231725 |
Correction on Trace Activation IE |
Huawei, Deutsche Telekom, Orange, CMCC |
| R3-231726 |
Correction on Trace Activation IE |
Huawei, Deutsche Telekom, Orange, CMCC |
| R3-231727 |
Discussion on the presence of area scope in MDT configuration |
Huawei, CMCC, China Unicom |
| R3-231728 |
Correction on the Area Scope IE in MDT Configuration |
Huawei, CMCC, China Unicom |
| R3-231729 |
Correction on the Area Scope IE in MDT Configuration |
Huawei, CMCC, China Unicom |
| R3-231730 |
[draft] LS on the presence of area scope |
Huawei |
| R3-231861 |
CB: # 4_R17SONMDT- Summary of email discussion |
Huawei - moderator |
| R3-231972 |
Correction on RESOURCE STATUS FAILURE message over E1 in Rel-16 |
ZTE, China Telecom, CMCC, Lenovo, China Unicom |
| R3-231973 |
Correction on RESOURCE STATUS FAILURE message over E1 in Rel-17 |
ZTE, China Telecom, CMCC, Lenovo, China Unicom |
| R3-231974 |
Correction on Event-based Reporting for Inter-system Resource Status Request |
ZTE, Nokia, Nokia Shanghai Bell, China Telecom, CMCC, Lenovo |
| R3-232055 |
F1AP Rel-17 correction for NR-U metrics |
Ericsson, Qualcomm Incorporated, Samsung, Nokia, Nokia Shanghai Bell |
| R3-232056 |
XnAP Rel-17 correction for NR-U metrics |
Ericsson, Qualcomm Incorporated, Samsung, Nokia, Nokia Shanghai Bell |
| R3-232058 |
Correction on Mobility Change procedure |
Huawei, Nokia, Nokia Shanghai Bell, Deutche Telekom, Qualcomm, ZTE, Orange, Vodafone |
| R3-232059 |
Correction on Mobility Change procedure |
Huawei, Nokia, Nokia Shanghai Bell, Deutche Telekom, Qualcomm, ZTE, Orange, Vodafone |
| R3-232095 |
Correction on Trace Activation IE |
Huawei, Deutsche Telekom, Orange, CMCC, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-232096 |
Correction on Trace Activation IE |
Huawei, Deutsche Telekom, Orange, CMCC, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-232097 |
Correction on the Area Scope IE in MDT Configuration |
Huawei, CMCC, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-232098 |
Correction on the Area Scope IE in MDT Configuration |
Huawei, CMCC, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| 9.2.2 |
MBS |
|
| R3-231114 |
Reply LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN |
RAN2, Nokia |
| R3-231293 |
Correction of MBS session at Xn handover |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange, CATT, ZTE |
| R3-231294 |
Correction of MBS session at Xn handover |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange, CATT, ZTE |
| R3-231295 |
Correction of MBS session at Xn handover |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange, CATT, ZTE |
| R3-231296 |
LS on MBS session information at Xn handover |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange, CATT, ZTE |
| R3-231389 |
Correction on NG-U tunnel aspect for MBS session |
Huawei, CBN, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-231390 |
Correction on Multicast session establishment |
Huawei, CBN, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-231391 |
Correction on Broadcast Partial Success |
Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-231392 |
Delay issue on initialization of initialRX-DELIV |
Huawei, CBN, China Unicom, Samsung, Lenovo |
| R3-231393 |
Correction on the delay issue on initialization of initialRX-DELIV |
Huawei, CBN, China Unicom, Samsung, Lenovo |
| R3-231394 |
[DRAFT] LS on the delay issue on initialization of initialRX-DELIV |
Huawei |
| R3-231401 |
Correction of MBS multicast HFN SN Initialisation |
Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated |
| R3-231402 |
Correction of MBS multicast HFN SN Initialisation |
Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated |
| R3-231403 |
LS on Multicast HFN/SN Initialization for Inactive Multicast Sessions |
Nokia, Nokia Shanghai Bell, orange, qualcomm, CATT |
| R3-231404 |
Resolution of MRB PDCP Wrap Around issue |
Nokia, Nokia Shanghai Bell |
| R3-231461 |
Discussion on MRB PDCP count “wrap around” problem |
CATT,CBN |
| R3-231462 |
Correction on MRB PDCP count “wrap around” problem |
CATT, CBN |
| R3-231502 |
Correction on multicast session distribution setup procedure in TS 38.413 |
ZTE |
| R3-231806 |
Correction on NR MBS multicast information |
CMCC, Huawei, ZTE |
| R3-231833 |
Clarifiication on RNTI assignment for MBS |
Google Inc. |
| R3-231834 |
Transfer of MBSInterestIndication from CU to DU |
Google Inc. |
| R3-231860 |
Response to R3-231392 and R3-231401 on delay of PDCP initialization |
ZTE |
| R3-231862 |
CB: # 5_R17MBS- Summary of email discussion |
Nokia - moderator |
| R3-231891 |
Response to R3-231461 and R3-231404 on PDCP COUNT wrap-around |
ZTE |
| R3-231965 |
Correction on Broadcast Partial Success |
Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-231966 |
Transfer of MBSInterestIndication from CU to DU |
Google Inc. |
| R3-232000 |
Correction on Multicast session establishment |
Huawei, CBN, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson |
| 9.2.4 |
Others |
|
| R3-231105 |
Reply LS on RB set configuration |
RAN1, ZTE |
| R3-231117 |
LS on the use of PEI during an emergency PDU session |
RAN2, Ericsson |
| R3-231118 |
Reply LS on applicability of timing error margin of Rx TEG |
RAN4, CATT |
| R3-231119 |
LS on Excess Packet Delay Threshold for MDT |
SA5, Nokia |
| R3-231124 |
Reply LS on introduction of a new attribute “Only Resource Coordination” to support source coordination between LTE and NR SA |
SA5, China telecom |
| R3-231221 |
Corrections on TNL association addition, update and removal (E1) |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung |
| R3-231222 |
Corrections on TNL association addition, update and removal (E1) |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung |
| R3-231223 |
Corrections on TNL association addition, update and removal (E1) |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung |
| R3-231224 |
Corrections on TNL association addition, update and removal (E1) |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, Samsung |
| R3-231229 |
Correction of Burst Arrival Time semantics description |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-231230 |
Correction of Burst Arrival Time semantics description |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-231231 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231232 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231240 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231241 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231242 |
Clarification on maximum length of Routing ID |
NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson |
| R3-231243 |
Clarification on maximum length of Routing ID |
NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson |
| R3-231244 |
Clarifications on TNLA Addition/Removal/Modification procedures |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231245 |
Clarification on the maximum length of Routing ID |
NTT DOCOMO, INC. |
| R3-231246 |
Clarification on usage of E-RAB Information List |
NTT DOCOMO, INC., Ericsson |
| R3-231247 |
Clarification on usage of E-RAB Information List |
NTT DOCOMO, INC., Ericsson |
| R3-231248 |
Clarification on usage of E-RAB Information List |
NTT DOCOMO, INC., Ericsson |
| R3-231249 |
Correction of Burst Arrival Time semantics description |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-231281 |
Discussion on multiple Trace Session activation |
CATT,ZTE,Huawei,CMCC,China Telecom |
| R3-231282 |
[Draft]LS to SA5 on multiple Trace Session Activation |
CATT,ZTE,Huawei.CMCC,China Telecom |
| R3-231291 |
Use of PEI during an Emergency PDU session |
Nokia, Nokia Shanghai Bell |
| R3-231311 |
Discussion on SA3 LS related to dynamic PSK for IAB inter-CU topology adaptation |
Qualcomm Inc. |
| R3-231314 |
Correction of Burst Arrival Time semantics description |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-231331 |
Corrections on TNL association addition and removal (X2AP) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-231332 |
Corrections on TNL association addition and removal (X2AP) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-231333 |
Corrections on TNL association (X2) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-231334 |
Corrections on TNL association (X2) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-231351 |
Corrections on TNL association addition, update and removal (F1AP) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231352 |
Corrections on TNL association addition, update and removal (F1AP) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231353 |
Corrections on TNL association addition, update and removal (F1) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231354 |
Corrections on TNL association addition, update and removal (F1) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-231360 |
Correction to TS 38.423 on RB Set Configuration |
ZTE, Lenovo, Qualcomm, Nokia, Nokia Shanghai Bell, CATT |
| R3-231361 |
Correction to TS 38.473 on RB Set Configuration |
ZTE, Lenovo, Qualcomm, Nokia, Nokia Shanghai Bell, CATT |
| R3-231362 |
Introduction of the UE hashed ID to 38.423 |
ZTE, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-231363 |
Introduction of the UE hashed ID to 38.473 |
ZTE, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-231366 |
Correction of SIType List |
Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-231367 |
Correction of SIType List |
Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-231368 |
Correction of SIType List |
Huawei, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-231369 |
Correction of RRC Resume Cause in PATH SWITCH REQUEST message |
Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-231370 |
Correction of RRC Resume Cause in PATH SWITCH REQUEST message |
Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-231371 |
Correction to RRC Inactive to other states |
Google |
| R3-231380 |
Clarification of the length of the Routing ID |
NEC |
| R3-231405 |
Correction of signalling only RA-based SDT |
Nokia, Nokia Shanghai Bell |
| R3-231406 |
Correction of signalling only RA-based SDT |
Nokia, Nokia Shanghai Bell |
| R3-231408 |
ASN.1 Correction of PRACH Configuration |
China Telecom,ZTE,CATT |
| R3-231414 |
ASN.1 Correction of PRACH Configuration |
China Telecom, ZTE,CATT |
| R3-231480 |
Correction on IAB bar configuration |
Huawei |
| R3-231481 |
Correction on IAB bar configuration |
Huawei, Qualcomm, Xiaomi |
| R3-231490 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231491 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231492 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231493 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231495 |
Discussion on the F1-C IP addresses mapping issue from SA3 LS R3-230872 |
Huawei |
| R3-231541 |
Missing transmission bandwidth configurations in XnAP [NR_FR1_35MHz_45MHz_BW] |
Ericsson, AT&T, Qualcomm, China Telecom, China Unicom, Samsung, CATT, CMCC, Nokia, Nokia Shanghai Bell |
| R3-231542 |
Missing transmission bandwidth configurations in X2AP [NR_FR1_35MHz_45MHz_BW] |
Ericsson, AT&T, Qualcomm, China Telecom, China Unicom, Samsung, CATT, CMCC, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-231543 |
Analysis of ACL remaining issues |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-231544 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-231545 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-231564 |
Issues on calculating eDRX PTW position for RRC_INACTIVE Ues |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231565 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231566 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231567 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231568 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231569 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231570 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX (stage 2) |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-231578 |
Correction of signalling only RA-based SDT |
Nokia, Nokia Shanghai Bell |
| R3-231579 |
[DRAFT] Reply LS on introduction of a new attribute "Only Resource Coordination" to support source coordination between LTE and NR SA |
China Telecom,Huawei |
| R3-231580 |
Clarification of Use Case and the Effect of the new Attribute “Only Resource Coordination” |
China Telecom,Huawei |
| R3-231596 |
Subcarrier Spacing FR2 correction |
Huawei |
| R3-231601 |
Discussion on new attribute “Only Resource Coordination |
Ericsson |
| R3-231610 |
Correction on F1AP for L2 U2N Relay |
Philips International B.V. |
| R3-231613 |
Correction on F1AP for L2 U2N Relay |
Philips International B.V. |
| R3-231614 |
Correction on F1AP for L2 U2N Relay |
Philips International B.V. |
| R3-231621 |
Correction on L2 U2N Relay Remote UE RRC procedures |
Philips International B.V. |
| R3-231634 |
Clarification of Application Layer Measurement Collection |
Nokia, Nokia Shanghai Bell |
| R3-231635 |
(CR TS 38.423) Correction of RB Set Configuration |
Ericsson |
| R3-231636 |
Correction of SDT with UE context relocation |
Ericsson, ZTE, China Telecom |
| R3-231637 |
Discussion on support of preconfigured GAPs for different configured BWP for RedCap UE |
Ericsson, Qualcomm Incorporated, CATT |
| R3-231638 |
Support of preconfigured Measurement GAPs for RedCap UE |
Ericsson, Qualcomm Incorporated, CATT |
| R3-231646 |
Discussion on the use of PEI during an emergency PDU session |
Ericsson, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-231647 |
Disabling UE-ID based PEI during emergency PDU session |
Ericsson, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-231648 |
Disabling UE-ID based PEI during emergency PDU session |
Ericsson, Deutsche Telekom, Verizon Wireless |
| R3-231649 |
Reply LS on the use of PEI during an emergency PDU session |
Ericsson |
| R3-231663 |
Correction of Priority Level |
Huawei, Deutsche Telekom, Orange, BT |
| R3-231664 |
Correction of Priority Level |
Huawei, Deutsche Telekom, Orange, BT |
| R3-231665 |
Correction of Priority Level |
Huawei, Deutsche Telekom, Orange, BT |
| R3-231666 |
Correction of RAT type in Data Usage Report List |
Huawei, Deutsche Telekom, BT |
| R3-231667 |
Correction of RAT type in Data Usage Report List |
Huawei, Deutsche Telekom, BT |
| R3-231668 |
Correction of RAT type in Data Usage Report List for Rel-17 |
Huawei, Deutsche Telekom, BT |
| R3-231688 |
Correction on SI delivery to RedCap UE during handover |
ZTE, China Telecom, CMCC |
| R3-231702 |
Reply LS on introduction of a new attribute to support source coordination between LTE and NR SA |
ZTE |
| R3-231703 |
Discussion on Correction on Packet Delay Budget |
ZTE, CATT,China Telecom |
| R3-231704 |
Correction on Packet Delay Budget |
ZTE, CATT,China Telecom |
| R3-231705 |
Correction on Packet Delay Budget |
ZTE, CATT,China Telecom |
| R3-231706 |
Correction on Packet Delay Budget |
ZTE, CATT,China Telecom |
| R3-231707 |
Correction on Packet Delay Budget |
ZTE, CATT,China Telecom |
| R3-231712 |
Discussion on the use of PEI during an emergency PDU session |
Huawei, China Unicom, China Telecom |
| R3-231713 |
[Draft] Reply LS on the use of PEI during an emergency PDU session |
Huawei |
| R3-231714 |
Disabling PEI during an emergency PDU session |
Huawei, China Unicom, China Telecom |
| R3-231715 |
Disabling PEI during an emergency PDU session |
Huawei, China Unicom, China Telecom |
| R3-231731 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Ericsson, Orange |
| R3-231732 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Ericsson, Orange |
| R3-231733 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Ericsson, Orange |
| R3-231734 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231735 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231736 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231737 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231738 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231739 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231748 |
Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters |
Huawei, Deutsche Telekom, Orange, BT |
| R3-231749 |
Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters |
Huawei, Deutsche Telekom, Orange, BT |
| R3-231750 |
Correction of Paging Priority Indicator in QoS Flow Level QoS Parameters |
Huawei, Deutsche Telekom, Orange, BT |
| R3-231752 |
Discussion on corrections for UP security policy update in MR-DC |
ZTE, China Telecom, CATT, China Unicom |
| R3-231753 |
Correction for UP security policy update in modification procedure |
ZTE, China Telecom, CATT, China Unicom |
| R3-231754 |
Correction for UP security policy update in modification procedure |
ZTE, China Telecom, CATT, China Unicom |
| R3-231755 |
Correction for UP security policy update in modification procedure |
ZTE, China Telecom, CATT, China Unicom |
| R3-231774 |
Correction of QoE stage-2 description |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Huawei, CATT |
| R3-231786 |
ASN.1 Correction of PRACH Configuration |
China Telecom,ZTE,CATT |
| R3-231787 |
Discussion on SA3 LS on Mapping of F1-C IP addresses |
ZTE |
| R3-231788 |
[draft] Reply LS on Mapping of F1-C IP addresses |
ZTE |
| R3-231804 |
Discussion on exchanging AMF Set information over Xn |
CMCC, Huawei |
| R3-231805 |
Correction on AMF Set Information over Xn |
CMCC, Huawei |
| R3-231845 |
Correction on behaviour procedure text for UP security procedure |
ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell |
| R3-231846 |
Correction on behaviour procedure text for UP security procedure |
ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell |
| R3-231847 |
Correction on behaviour procedure text for UP security procedure |
ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell |
| R3-231855 |
(CR TS 38.423) Correction of RB Set Configuration |
Ericsson |
| R3-231856 |
Correction on IAB bar configuration |
Huawei, Qualcomm, Xiaomi |
| R3-231863 |
CB: # 6_R17IAB- Summary of email discussion |
ZTE - moderator |
| R3-231864 |
CB: # 7_PEI- Summary of email discussion |
Ericsson - moderator |
| R3-231865 |
CB: # 8_NewAttribute- Summary of email discussion |
China Telecom - moderator |
| R3-231866 |
CB: # 9_TNLAssociation- Summary of email discussion |
Nokia - moderator |
| R3-231867 |
CB: # 10_HashedUEID- Summary of email discussion |
CATT - moderator |
| R3-231907 |
Support of preconfigured Measurement GAPs for RedCap UE |
Ericsson, Qualcomm Incorporated, CATT |
| R3-231910 |
Missing transmission bandwidth configurations in XnAP [NR_FR1_35MHz_45MHz_BW] |
Ericsson, AT&T, Qualcomm, China Telecom, China Unicom, Samsung, CATT, CMCC, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-231911 |
Missing transmission bandwidth configurations in X2AP [NR_FR1_35MHz_45MHz_BW] |
Ericsson, AT&T, Qualcomm, China Telecom, China Unicom, Samsung, CATT, CMCC, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-231912 |
CB: # 49_QoEStage2 |
ZTE |
| R3-231913 |
Clarification on maximum length of Routing ID |
NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson |
| R3-231914 |
Clarification on maximum length of Routing ID |
NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson |
| R3-231915 |
Clarification on the maximum length of Routing ID |
NTT DOCOMO, INC. |
| R3-231916 |
CB: # 50_UPSecurity |
ZTE |
| R3-231917 |
Correction of Burst Arrival Time semantics description |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-231918 |
CB: # 51_MultiTrace |
CATT |
| R3-231920 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231921 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231922 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-231923 |
CB: # 53_ACL |
Ericsson |
| R3-231924 |
CB: # 55_PDB |
ZTE |
| R3-231925 |
CB: # 56_QoEALMC |
Nokia |
| R3-231926 |
CB: # 57_BWPConfig |
Ericsson |
| R3-231927 |
Correction of Priority Level |
Huawei, Deutsche Telekom, Orange, BT, Nokia, Nokia Shanghai Bell |
| R3-231928 |
CB: # 58_DataUsage Report |
Huawei |
| R3-231929 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Ericsson, Orange, ZTE, Deutsche Telekom |
| R3-231930 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Ericsson, Orange, ZTE, Deutsche Telekom |
| R3-231931 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Ericsson, Orange, ZTE, Deutsche Telekom |
| R3-231932 |
CB: 59_ResourceCoordination |
Huawei |
| R3-231986 |
Correction of RAT type in Data Usage Report List |
Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell |
| R3-231987 |
Correction of RAT type in Data Usage Report List |
Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell |
| R3-231988 |
Correction of RAT type in Data Usage Report List for Rel-17 |
Huawei, Deutsche Telekom, BT, Nokia, Nokia Shanghai Bell |
| R3-231990 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231991 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231992 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231993 |
Clarifications on TNLA Addition/Removal/Modification procedures (XnAP) |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-232003 |
Correction on Packet Delay Budget |
ZTE, CATT,China Telecom |
| R3-232006 |
Corrections on TNL association addition, update and removal (F1AP) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232007 |
Corrections on TNL association addition, update and removal (F1AP) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232008 |
Corrections on TNL association addition, update and removal (F1) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232009 |
Corrections on TNL association addition, update and removal (F1) |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232010 |
Correction on Extended Packet Delay Budget |
Nokia, Nokia Shanghai Bell, ZTE, CATT, China Telecom, Ericsson, Huawei |
| R3-232012 |
Introduction of the UE hashed ID to 38.423 |
ZTE, Nokia, Nokia Shanghai Bell, China Telecom, CATT, Huawei, Ericsson, Qualcomm |
| R3-232013 |
Introduction of the UE hashed ID to 38.473 |
ZTE, Nokia, Nokia Shanghai Bell, China Telecom, CATT, Huawei, Ericsson, Qualcomm |
| R3-232014 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232015 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232016 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232017 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX (stage 2) |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232018 |
Correction of Extended Packet Delay Budget |
ZTE, CATT,China Telecom, Nokia , Nokia Shanghai Bell, Ericsson, Huawei |
| R3-232019 |
Correction of Extended Packet Delay Budget |
ZTE, CATT,China Telecom, Nokia , Nokia Shanghai Bell, Ericsson, Huawei |
| R3-232024 |
Correction on Extended Packet Delay Budget |
Ericsson, ZTE, CATT, China Telecom, Nokia, Nokia Shanghai Bell, Huawei |
| R3-232031 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232032 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232033 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232034 |
Corrections on TNL association addition, update and removal |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-232042 |
Corrections on TNL association addition and removal (X2AP) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-232043 |
Corrections on TNL association addition and removal (X2AP) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-232044 |
Corrections on TNL association (X2) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-232045 |
Corrections on TNL association (X2) |
Samsung, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-232048 |
Correction of QoE stage-2 description |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Huawei, CATT, Samsung |
| R3-232049 |
ASN.1 Correction of PRACH Configuration |
China Telecom,ZTE,CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-232050 |
ASN.1 Correction of PRACH Configuration |
China Telecom,ZTE,CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-232051 |
[DRAFT] Reply LS on introduction of a new attribute "Only Resource Coordination" to support source coordination between LTE and NR SA |
China Telecom |
| R3-232053 |
Correction of RRC Resume Cause in PATH SWITCH REQUEST message |
Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated |
| R3-232054 |
Correction of RRC Resume Cause in PATH SWITCH REQUEST message |
Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated |
| R3-232064 |
Correction on behaviour procedure text for UP security procedure |
ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-232065 |
Correction for UP security policy update in modification procedure |
ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung |
| R3-232073 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom |
| R3-232074 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell |
| R3-232075 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell |
| R3-232076 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell |
| R3-232077 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell |
| R3-232078 |
Correction on E-UTRA - NR Cell Resource Coordination |
Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell |
| R3-232080 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-232081 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-232117 |
Reply LS on Mapping of F1-C IP addresses in the IAB inter-CU topology adaptation and backhaul RLF recovery procedures |
RAN3(ZTE) |
| R3-232127 |
Clarification of Application Layer Measurement Collection |
Nokia, Nokia Shanghai Bell |
| R3-232128 |
Correction on behaviour procedure text for UP security procedure |
ZTE, China Telecom, CATT, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-232130 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232131 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232132 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232133 |
Introduction of Hashed UE Identity Index Value for RRC_INATIVE with eDRX (stage 2) |
CATT, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-232134 |
CB: # 10_HashedUEID- Summary of email discussion |
CATT - moderator |
| R3-232135 |
ASN.1 Correction of PRACH Configuration |
China Telecom,ZTE,CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-232136 |
ASN.1 Correction of PRACH Configuration |
China Telecom, ZTE,CATT |
| R3-232153 |
Correction on Extended Packet Delay Budget |
Nokia, Nokia Shanghai Bell, ZTE, CATT, China Telecom, Ericsson, Huawei |
| R3-232154 |
Correction on Extended Packet Delay Budget |
Ericsson, ZTE, CATT, China Telecom, Nokia, Nokia Shanghai Bell, Huawei |
| R3-232156 |
CB: # 53_ACL |
Ericsson |
| R3-232157 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-232158 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-232163 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-232164 |
Missing Use Cases for Dynamic ACL |
Ericsson, Deutsche Telekom, Huawei, China Telecom |
| R3-232166 |
Reply LS on Mapping of F1-C IP addresses in the IAB inter-CU topology adaptation and backhaul RLF recovery procedures |
RAN3(ZTE) |
| R3-232167 |
Correction to TS 38.423 on RB Set Configuration |
ZTE, Lenovo, Qualcomm, Nokia, Nokia Shanghai Bell, CATT |
| R3-232168 |
Correction to TS 38.473 on RB Set Configuration |
ZTE, Lenovo, Qualcomm, Nokia, Nokia Shanghai Bell, CATT |
| R3-232170 |
Clarification on the maximum length of Routing ID |
NTT DOCOMO, INC. |
| 10.1 |
General |
|
| R3-231125 |
(BLCR to 38.423) Addition of SON features enhancement |
Samsung |
| R3-231126 |
(BLCR to 38.473) Addition of SON features enhancement |
Huawei |
| R3-231127 |
BLCR to 38.300:enhancement of SON |
CMCC |
| R3-231128 |
(BLCR to 38.413) for SON |
Ericsson |
| R3-231129 |
(BLCR to 38.401) Addition of SON features enhancement |
ZTE |
| R3-231789 |
Update of work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI |
CMCC |
| R3-231906 |
(BLCR to 38.413) for SON |
Ericsson |
| 10.2.1 |
SHR and SPR |
|
| R3-231189 |
[TP to 38.423, SON] Configuration coordination for the successful PSCell change report |
Nokia Netherlands |
| R3-231200 |
(TP for SON BLCR for 38.423) SON enhancement for SHR and SPR |
Samsung |
| R3-231269 |
(TPs for SON BLCRs for TS 38.300) SHR |
Huawei |
| R3-231270 |
(TPs for SON BLCRs for TS 38.300) SPR |
Huawei |
| R3-231299 |
Inter-RAT SHR and SPR |
Intel Corporation |
| R3-231339 |
Successful Handover Report and Successful PSCell Change Report |
Qualcomm Incorporated |
| R3-231372 |
Discussion on related issue of inter-RAT SHR |
NEC |
| R3-231423 |
SON enhancements for SPR |
Lenovo |
| R3-231424 |
SON enhancements for SHR |
Lenovo |
| R3-231552 |
Discussion on SON enhancement for SHR and SPR |
CATT |
| R3-231584 |
Inter-RAT SHR and SPR discussion |
Ericsson |
| R3-231708 |
(TPs for SON BLCRs for TS 38.300 TS 38.413 TS 38.473 and TS 38.423)Inter-RAT SHR and SPR |
ZTE |
| R3-231791 |
SON enhancement for Inter-RAT SHR |
CMCC |
| R3-231792 |
SON enhancement for SPR |
CMCC |
| R3-231868 |
CB: # SONMDT1_SHRSPR- Summary of email discussion |
Qualcomm - moderator |
| R3-232002 |
(TP for SON BLCR for 38.423) SON enhancement for SHR and SPR |
Samsung |
| R3-232004 |
CB: # SONMDT1_SHRSPR- Summary of email discussion |
Qualcomm - moderator |
| R3-232021 |
(TPs for SON BLCRs for TS 38.413 )Inter-RAT SHR and SPR |
ZTE, Qualcomm |
| R3-232022 |
(TPs for SON BLCRs for TS 38.473) Inter-RAT SHR and SPR |
ZTE, Qualcomm |
| R3-232060 |
(TPs for SON BLCRs for TS 38.300) SHR |
Huawei |
| R3-232061 |
LS on intra-system inter-RAT SHR and on SPR |
Huawei |
| R3-232137 |
(TPs for SON BLCRs for TS 38.473) Inter-RAT SHR and SPR |
ZTE, Qualcomm, Samsung |
| R3-232140 |
LS on intra-system inter-RAT SHR and on SPR |
Huawei |
| 10.2.2 |
MRO |
|
| R3-231201 |
(TP for SON BLCR for 37.340 and 38.423) SON enhancements for CPAC and MCG failure recovery |
Samsung |
| R3-231202 |
(TP for SON BLCR for 38.413 and 38.300) MRO for inter-system handover for voice fallback |
Samsung |
| R3-231226 |
[TP to 37.340, SON] Further consideration on the CPC Execution to wrong PSCell |
Nokia, Nokia Shanghai Bell |
| R3-231227 |
[TP to TS38423, SON] Support for MRO for fast MCG recovery in case of SCG deactivation and for pre-Rel.18 UEs |
Nokia, Nokia Shanghai Bell |
| R3-231271 |
(TPs for SON BLCRs for TS 38.300): MRO related objectives |
Huawei |
| R3-231340 |
MRO enhancements for CPAC, voice fallback and fast MCG recovery |
Qualcomm Incorporated |
| R3-231373 |
Discussion on remaining issue of MRO for fast MCG recovery |
NEC |
| R3-231425 |
(TP for SON BLCR for 37.340) SON enhancements for CPAC |
Lenovo |
| R3-231426 |
(TP for SON BLCR for 38.300) MRO for inter-system handover for voice fallback |
Lenovo, CMCC |
| R3-231427 |
MRO for fast MCG link recovery |
Lenovo |
| R3-231553 |
Discussion on MRO for CPAC |
CATT |
| R3-231554 |
Discussion on MRO for fast MCG recovery and voice fallback |
CATT |
| R3-231585 |
(TP for SON BL CR for TS 36.300, TS 38.300, TS 38.423) SON enhancements for MRO |
Ericsson |
| R3-231689 |
(TPs for SON BL CR TS37.340 and TS38.413) MRO enhancemetns in Rel-18 |
ZTE |
| R3-231790 |
MRO for CPC and CPA |
CMCC |
| R3-231800 |
Further considerations on fast MCG recovery |
CMCC |
| R3-231869 |
CB: # SONMDT2_MRO- Summary of email discussion |
Nokia - moderator |
| R3-232001 |
(TP for SON BLCR for 37.340) UHI for CPAC |
Samsung |
| R3-232011 |
CB: # SONMDT2_MRO- Summary of email discussion |
Nokia - moderator |
| R3-232062 |
[TP to 37.340, SON] Definitions for MRO failure events for CPAC |
Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Ericsson, Samsung |
| R3-232147 |
Update of WF on the MRO scenarios |
Lenovo |
| R3-232151 |
(TP for SON BL CR for TS 38.300) SON enhancements for MRO |
Ericsson |
| 10.2.3 |
RACH Enhancements |
|
| R3-231112 |
Reply LS on RACH enhancement for R18 SONMDT |
RAN2, Huawei |
| R3-231203 |
Discussion on SON for RACH |
Samsung |
| R3-231300 |
(TP for SON BL CR for TS 38.473) RACH enhancements |
Intel Corporation |
| R3-231341 |
RACH optimization enhancements |
Qualcomm Incorporated |
| R3-231555 |
Discussion on RACH enhancement |
CATT |
| R3-231586 |
RACH Optimization enhancement |
Ericsson |
| R3-231587 |
Reply LS on RACH enhancement for R18 SONMDT |
Ericsson |
| R3-231628 |
(TP for SON BL CR to TS 38.473) Further discussion on RACH optimisation |
Nokia, Nokia Shanghai Bell |
| R3-231709 |
(TPs for SON BLCRs for TS 38.473 and TS 38.423)RACH enhancements |
ZTE |
| R3-231740 |
(TPs for SON BLCRs for TS 38.300, TS 38.401, TS 38.423, TS 36.423,TS 38.473): Remaining issues for RACH optimisation |
Huawei |
| R3-231741 |
[draft] Rely LS on RACH enhancement for R18 SONMDT |
Huawei |
| R3-231870 |
CB: # SONMDT3_RACH- Summary of email discussion |
Intel - moderator |
| R3-231999 |
(TP for SON BL CR to TS 38.473) Further discussion on RACH optimisation |
Nokia, Nokia Shanghai Bell |
| R3-232020 |
(TPs for SON BLCRs for TS 38.423)RACH enhancements |
ZTE, Intel |
| R3-232025 |
CB: # SONMDT3_RACH- Summary of email discussion |
Intel Corporation (moderator) |
| R3-232099 |
(TPs for SON BLCR for TS 38.300): Naming update for RA report |
Huawei |
| R3-232100 |
[draft] Rely LS on RACH enhancement for R18 SONMDT |
Huawei |
| R3-232101 |
(TPs for SON BLCR for TS 38.401): Naming update for RA report |
Huawei |
| R3-232102 |
(TPs for SON BLCR for TS 38.423): Naming update for RA report |
Huawei |
| R3-232103 |
(TPs for SON BLCR for TS 38.473): Naming update for RA report |
Huawei |
| R3-232104 |
(TPs for SON BLCR for TS 36.423): Naming update for RA report |
Huawei |
| R3-232141 |
(TP for SON BL CR to TS 38.473) TP for RACH optimisation |
Nokia, Nokia Shanghai Bell, Huawei, ZTE, Intel, Ericsson |
| R3-232142 |
(TPs for SON BLCRs for TS 38.423)RACH enhancements |
ZTE, Intel, Ericsson |
| R3-232143 |
(TPs for SON BLCR for TS 38.423): Naming update for RA report |
Huawei |
| R3-232144 |
[draft] Rely LS on RACH enhancement for R18 SONMDT |
Huawei |
| 10.2.4 |
SON/MDT Enhancements for Non-Public Networks |
|
| R3-231184 |
(TP for MDT BL CR for TS 38.423) Addition of PNI-NPN in MDT Area Scope |
Huawei, China Telecom, CMCC |
| R3-231185 |
(TP for SON BLCR for TS 37.320): MDT support in SNPN |
Huawei, Orange, China Telecom, CMCC |
| R3-231301 |
(TP for SON BL CR for TS 38.413) MDT enhancements for SNPN |
Intel Corporation |
| R3-231337 |
Discussion on SON/MDT for NPN |
BEIJING SAMSUNG TELECOM R&D |
| R3-231342 |
SON MDT enhancements for Non-Public networks |
Qualcomm Incorporated |
| R3-231556 |
Discussion on SONMDT enhancement for NPN |
CATT |
| R3-231588 |
SON enhancements for Non-public networks |
Ericsson |
| R3-231629 |
(TP for MDT BL CR to TS 38.413) Support of NPN in MDT area scope |
Nokia, Nokia Shanghai Bell |
| R3-231710 |
(TPs for SON BLCRs for TS 38.413 and TS 38.423)MDT support in NPN |
ZTE |
| R3-231742 |
(TPs for MDT BLCRs for TS 38.413, TS 38.423): MDT support in SNPN |
Huawei |
| R3-231871 |
CB: # SONMDT4_NPN- Summary of email discussion |
ZTE - moderator |
| R3-232027 |
(TPs for MDT BLCRs for TS 38.413)MDT support in NPN |
ZTE |
| R3-232091 |
(TP for MDT BL CR for TS 38.423) Addition of PNI-NPN in MDT Area Scope |
Huawei, China Telecom, CMCC |
| R3-232112 |
CB: # SONMDT4_NPN- Summary of email discussion |
ZTE - moderator |
| R3-232118 |
LS on potential override of logged MDT reports upon moving from SNPN to PLMN |
RAN3(Ericsson) |
| 10.2.5 |
SON for NR-U |
|
| R3-231204 |
Discussion on SON for NR-U |
Samsung |
| R3-231228 |
The LBT waiting time for correct NR-U MRO analysis |
Nokia, Nokia Shanghai Bell |
| R3-231302 |
NR-U enhancements for MRO |
Intel Corporation |
| R3-231343 |
SON enhancements for NR-U |
Qualcomm Incorporated |
| R3-231428 |
Discussion on MRO for NR-U |
Lenovo |
| R3-231557 |
Discussion on SON enhancement for NR-U |
CATT |
| R3-231589 |
Radio Resource Status per NR-U Channel |
Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated |
| R3-231590 |
(TP for SON BL CR for TS 38.423) Radio Resource Status per NR-U Channel |
Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated |
| R3-231591 |
(TP for SON BL CR for TS 38.473) Radio Resource Status per NR-U Channel |
Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated |
| R3-231592 |
(TP for SON BL CR for TS 38.423) NR-U metrics |
Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung |
| R3-231593 |
(TP for SON BL CR for TS 38.473) NR-U metrics |
Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung |
| R3-231594 |
NR-U enhancements for MRO and MLB |
Ericsson |
| R3-231690 |
Further discussion on NR-U optimizations |
ZTE |
| R3-231743 |
(TPs for SON BLCR for TS 38.423, TS 38.473): SON for NR-U |
Huawei |
| R3-231872 |
CB: # SONMDT5_NRU- Summary of email discussion |
Ericsson - moderator |
| R3-231996 |
(TP for SON BL CR for TS 38.423) NR-U metrics |
Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung |
| R3-231997 |
(TP for SON BL CR for TS 38.473) NR-U metrics |
Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung |
| R3-232067 |
(TP for SON BL CR for TS 38.423) NR-U metrics |
Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung |
| R3-232068 |
(TP for SON BL CR for TS 38.473) NR-U metrics |
Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung |
| R3-232069 |
CB: # SONMDT5_NRU- Summary of email discussion |
Ericsson - moderator |
| 10.2.6 |
MDT Enhancements |
|
| R3-231711 |
(TPs for MDT BLCRs for TS 38.413)MDT Enhancements |
ZTE |
| R3-231744 |
(TP for MDT BL CR for TS 38.413): Signalling based immediate MDT in NR-DC |
Huawei, Deutsche Telekom, Orange, China Telecom, CMCC |
| R3-231873 |
CB: # SONMDT6_MDT- Summary of email discussion |
Huawei - moderator |
| R3-231995 |
LS on MDT measurements collection in MR-DC |
Huawei |
| R3-232070 |
LS on MDT measurements collection in MR-DC |
Huawei |
| 11.1 |
General |
|
| R3-231110 |
LS on Continuity of QoE measurements during intra-5GC inter-RAT HO |
RAN2, Huawei |
| R3-231130 |
(BLCR) Enhancement on NR QoE |
Samsung |
| R3-231131 |
(BLCR) Enhancement on NR QoE |
ZTE Corporation |
| R3-231132 |
(BLCR to 38.300) for QoE Enh |
China Unicom |
| R3-231422 |
Discussion on QoE measurement during intra-5GC inter-RAT handover |
Lenovo |
| R3-231763 |
Discussion on the support of QoE continuity during intra-5GC inter RAT handover |
Huawei |
| R3-231764 |
[draft] Reply LS to LS on Continuity of QoE measurements during intra-5GC inter-RAT HO |
Huawei |
| R3-231775 |
Dicussion on the LS from RAN2 about QoE continuity in intra-5GC inter-RAT HO |
ZTE |
| R3-231827 |
Update Workplan for Rel-18 NR QoE Enhancement |
China Unicom |
| R3-231874 |
CB: # QoE1_BLCR_RAN2LS - Summary of email discussion |
China Unicom - moderator |
| R3-231945 |
(BLCR to 38.300) for QoE Enh |
China Unicom |
| 11.2 |
Support for New Service Type and RRC_INACTIVE/RRC_IDLE states |
|
| R3-231120 |
Reply LS on QoE measurements in RRC IDLE/INACTIVE states |
SA5, Huawei |
| R3-231216 |
Remaining open issues on QMC for MBS and RRC state |
Samsung |
| R3-231318 |
Discussion on NR QoE in RRC_INACTIVE/RRC_IDLE states |
CATT |
| R3-231344 |
QMC in RRC_INACTIVE and RRC_IDLE for MBS broadcast service |
Qualcomm Incorporated |
| R3-231345 |
QoE enhancements for high mobility scenarios |
Qualcomm Incorporated |
| R3-231429 |
Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states |
Lenovo |
| R3-231430 |
(TP to 38.423 & 38.420) Support of QoE measurement in RRC_INACTIVE |
Lenovo |
| R3-231486 |
QoE and RVQoE Measurement Support for MBS |
Ericsson |
| R3-231487 |
QMC in HSDN Cells and High Mobility Scenarios |
Ericsson |
| R3-231518 |
QoE configuration and reporting in RRC_INACTIVE RRC_IDLE states |
Xiaomi |
| R3-231519 |
Discussion on QoE in high mobility scenario |
Xiaomi |
| R3-231624 |
Information required for MBS BC QMC |
Nokia, Nokia Shanghai Bell, Orange |
| R3-231625 |
QMC support for high mobility scenarios |
Nokia, Nokia Shanghai Bell |
| R3-231768 |
[draft] Reply LS to Reply LS on QoE measurements in RRC IDLE/INACTIVE states |
Huawei |
| R3-231769 |
TP for 38300 BL CR on INACTIVE IDLE QoE new service types and high speed scenario |
ZTE, CMCC |
| R3-231770 |
Discussion on SA4 reply LS with draft reply LS |
ZTE, CMCC, China Unicom |
| R3-231771 |
Discussion on IDLE NACTIVE QoE and high mobility scenario |
ZTE, CMCC |
| R3-231819 |
Further discussions on the support of MBS QoE |
Huawei |
| R3-231820 |
(TP for NR_QoE BL CR for 38.300) on QoE measurement enhancements |
Huawei, China Telecom, China Unicom |
| R3-231821 |
CR to 38.413 on the introduction of R18 QoE measurement |
Huawei, China Telecom, China Unicom |
| R3-231828 |
Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states |
China Unicom |
| R3-231829 |
Discussion on QoE measurement for high mobility scenarios |
China Unicom |
| R3-231875 |
CB: # QoE2_InactiveIdle- Summary of email discussion |
Huawei - moderator |
| R3-231946 |
CB: # QoE2_InactiveIdle- Summary of email discussion |
Huawei - moderator |
| R3-232071 |
CR to 38.413 on the introduction of R18 QoE measurement |
Huawei, China Telecom, China Unicom |
| R3-232072 |
TP for 38300 BL CR on INACTIVE IDLE QoE new service types and high speed scenario |
ZTE, CMCC |
| R3-232079 |
LS on OAM awareness of MBS service area and MBS session ID |
Huawei |
| R3-232150 |
CB: # QoE2_InactiveIdle- Summary of email discussion |
Huawei - moderator |
| R3-232160 |
TP to BL CRs for TS 38.300 for INACTIVE/IDLE QoE, new service types, and high mobility scenario |
ZTE, CMCC, Huawei, China Telecom, China Unicom |
| 11.3 |
Support QoE for NR-DC |
|
| R3-231217 |
Remaining open issues on support of NR-DC |
Samsung |
| R3-231319 |
Discussion on Support for legacy QoE in NR-DC |
CATT |
| R3-231320 |
Discussion on Support for RV-QoE in NR-DC |
CATT |
| R3-231346 |
Support for QoE in NR-DC |
Qualcomm Incorporated |
| R3-231431 |
Discussion on QoE measurement in NR-DC |
Lenovo |
| R3-231488 |
(TP for QoE BL CR for TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios |
Ericsson |
| R3-231520 |
Discussion on QoE configuration and reporting in NR-DC |
Xiaomi |
| R3-231626 |
Further discussion on SN-triggered m-based QMC |
Nokia, Nokia Shanghai Bell |
| R3-231776 |
Further Consideration on QoE in NR-DC |
ZTE, China Telecom, CMCC |
| R3-231777 |
Dicussion on MDT alignment and mobility in NR-DC |
ZTE, China Telecom |
| R3-231778 |
TPs to BL CR of 38.401 and BL CR of 38.423 on NR QoE |
ZTE, China Telecom |
| R3-231818 |
Further discussions on the support for QoE in NR-DC |
Huawei |
| R3-231830 |
Further discussion on QoE measurement in NR-DC |
China Unicom |
| R3-231876 |
CB: # QoE3_NR-DC- Summary of email discussion |
Ericsson - moderator |
| R3-231919 |
(draftCR TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios |
Ericsson |
| R3-231947 |
CB: # QoE3_NR-DC- Summary of email discussion |
Ericsson - moderator |
| R3-232035 |
(TP for QoE BL CR for TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios |
Ericsson |
| 11.4 |
Left-over from R17 |
|
| R3-231111 |
LS on buffer level threshold-based RVQoE reporting |
RAN2, Apple |
| R3-231123 |
LS on Approval of eQoE CRs for NR |
SA5, Ericsson |
| R3-231321 |
Discussion on Left-over issues |
CATT |
| R3-231347 |
Enhancements to RAN visible QoE |
Qualcomm Incorporated |
| R3-231489 |
(TP for QoE BL CR for TS 38.473) Enhancements of Rel-17 QoE and RVQoE Features |
Ericsson |
| R3-231521 |
Discussion on RVQoE information (TP to BL CR TS 38.473 Enhancement on NR QoE) |
Xiaomi |
| R3-231627 |
(TP for BL CR to TS 38.473) Deactivation of RAN visible QoE information transfer via F1 |
Nokia, Nokia Shanghai Bell |
| R3-231762 |
Further discussion on the support of R17 left-over features |
Huawei |
| R3-231779 |
Discussion on left-over issues from R17 |
ZTE, China Unicom, China Telecom |
| R3-231780 |
TP to BL CR of 38.473 on NR QoE enhancement |
ZTE, China Unicom, China Telecom |
| R3-231831 |
Further discussion on assistance information when RAN overload |
China Unicom |
| R3-231877 |
CB: # QoE4_Others- Summary of email discussion |
ZTE - moderator |
| R3-232046 |
CB: # QoE4_Others- Summary of email discussion |
ZTE - moderator |
| R3-232047 |
LS on the feasibility of introducing assistance information for handling of QoE reporting during RAN overload |
ZTE |
| R3-232146 |
LS to RAN2 on threshold-based triggers and event-based triggers for RAN Visible QoE report |
RAN3(Qualcomm) |
| 12.1 |
General |
|
| R3-231133 |
(BLCR to 38.423) for AI/ML for NG-RAN |
Ericsson |
| R3-231134 |
CR to TS 38.401 for addition of AI/ML-RAN feature in the case of split architecture |
ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCC |
| R3-231135 |
(BLCR) Draft CR to 38.300 on AI/ML for NG-RAN |
CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation |
| 12.2.1 |
Stage2 Related |
|
| R3-231615 |
(TP for AI/ML BLCR to TS38.300) Characteristics of the procedures for exchanging AI/ML-related information |
Ericsson, InterDigital |
| R3-231655 |
(TP for TS 38.300) AI/ML General Aspects |
Nokia, Nokia Shanghai Bell, Orange |
| R3-231797 |
(TP for AIML BLCR to TS38.300) Stage 2 updates on the new procedures of AIML for RAN |
CMCC, CATT |
| R3-231822 |
(TP for AI&ML BLCR for TS 38.300) Further discussions on common issues and Stage 2 updates on the introduction of RAN AI/ML |
Huawei |
| R3-231823 |
Further discussions on remaining common open isses for the introduction of RAN AIML |
Huawei |
| R3-231841 |
(TP to BLCR for 38.300) Further discussion on AIML RAN function |
ZTE |
| R3-231878 |
CB: # AIRAN1_Stage2- Summary of email discussion |
CMCC - moderator |
| R3-232122 |
CB: # AIRAN1_Stage2- Summary of email discussion |
CMCC - moderator |
| R3-232125 |
(TP for AIML BLCR to TS38.300) Stage 2 updates on the new procedures of AIML for RAN |
CMCC, CATT, Nokia, Nokia Shanghai Bell, Lenovo, Ericsson, Huawei, Samsung |
| 12.2.2.1 |
LB and Xn procedures |
|
| R3-231205 |
Discussion on Xn impact of LB |
Samsung |
| R3-231209 |
TP to 38.423 for partial reporting of AI/ML information |
Samsung |
| R3-231259 |
Xn enhancements for NG-RAN AI-ML |
Qualcomm Incorporated |
| R3-231260 |
Feedback for NG-RAN AI-ML |
Qualcomm Incorporated |
| R3-231378 |
AIML Load balancing |
NEC |
| R3-231432 |
Miscellaneous Xn interface issues |
Lenovo |
| R3-231433 |
Discussion on prediction accuracy and time information |
Lenovo |
| R3-231434 |
Discussion on UE performance feedback collection |
Lenovo |
| R3-231465 |
Discussion on partial success and validity time |
CATT |
| R3-231469 |
(TP for 38.423) Updates on non-UE associated messages to support AI/ML |
CATT |
| R3-231515 |
Discussion on validity time and prediction accuracy |
China Telecommunication |
| R3-231602 |
AI-ML Event triggered UE performance reporting |
Ericsson, InterDigital, Deutsche Telekom |
| R3-231603 |
(TP for AI/ML BLCR to TS 38.423) AI-ML Event triggered UE performance reporting |
Ericsson, InterDigital, Deutsche Telekom |
| R3-231616 |
(TP for AI/ML BLCR to TS38.423) Partial success for the AI-ML Assistance Data Reporting procedure |
Ericsson, InterDigital |
| R3-231620 |
(TP for AI/ML BLCR to TS38.423) AI-ML Threshold Based Events |
Ericsson |
| R3-231656 |
(TP for TS 38.423) LB and AI/ML Information Exchange over Xn |
Nokia, Nokia Shanghai Bell |
| R3-231680 |
Further discussion on remaining issues on procedures for AI |
ZTE |
| R3-231681 |
(TP to 38.423 and 38.420) AIRAN impact on Xn Interface |
ZTE |
| R3-231795 |
Discussion on AIML UE performance feedback |
CMCC |
| R3-231796 |
(TP for 38.423)Procedure for AIML related Information |
CMCC |
| R3-231798 |
Remaining issues on predicted information |
CMCC |
| R3-231824 |
(TP for AIML BLCR for TS 38.423) Remaining open issues for load balancing |
Huawei |
| R3-231879 |
CB: # AIRAN2_LB- Summary of email discussion |
ZTE - moderator |
| R3-232023 |
CB: # AIRAN2_LB- Summary of email discussion |
ZTE - moderator |
| R3-232120 |
(TP to 38.423) AIRAN Impact on Xn Interface |
ZTE, Ericsson, Qualcomm Incorporated |
| R3-232148 |
(TP to 38.423) AIRAN Impact on Xn Interface |
ZTE, Ericsson, Qualcomm Incorporated |
| 12.2.2.2 |
ME and Xn procedures |
|
| R3-231206 |
Discussion on Xn impact of ME |
Samsung |
| R3-231376 |
AIML Mobility Enhancement |
NEC |
| R3-231435 |
Discussion on future UE trajectory collection |
Lenovo, Intel Corporation, ZTE |
| R3-231436 |
(TP for TS38.423) on future UE trajectory collection |
Lenovo |
| R3-231467 |
Discussion on XnAP impacts of AI/ML for UE associated metrics |
CATT |
| R3-231468 |
(TP for 38.423) Support of AI/ML based mobility optimization |
CATT |
| R3-231514 |
Discussion on AI/ML based mobility optimization |
China Telecommunication |
| R3-231538 |
Mobility Optimization Outputs |
InterDigital |
| R3-231539 |
(TP for AIML BLCR for TS 38.423) Mobility Optimization Outputs |
InterDigital Finland Oy |
| R3-231608 |
Cell based UE trajectory prediction exchange |
Ericsson, InterDigital, Qualcomm |
| R3-231609 |
(TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange |
Ericsson, InterDigital, Qualcomm |
| R3-231619 |
Open points on validity time and prediction accuracy |
Ericsson |
| R3-231650 |
Discussion on cell based UE trajectory prediction |
LG Electronics Inc. |
| R3-231651 |
(TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on cell based UE trajectory prediction |
LG Electronics Inc. |
| R3-231657 |
(TP for TS 38.423) AI/ML Mobility Optimization |
Nokia, Nokia Shanghai Bell |
| R3-231658 |
(TP for TS 38.423) Cell-based UE Trajectory Prediction |
Nokia, Nokia Shanghai Bell |
| R3-231683 |
Discussion on left issues of AI based mobility optimization |
ZTE |
| R3-231799 |
On Predicted UE Trajectory Information |
CMCC |
| R3-231825 |
(TP for AIML BLCR for TS 38.423) Remaining open issues for mobility enhancements |
Huawei |
| R3-231880 |
CB: # AIRAN3_ME- Summary of email discussion |
NEC - moderator |
| R3-232026 |
CB: # AIRAN3_ME- Summary of email discussion |
NEC - moderator |
| 12.2.2.3 |
ES and Xn procedures |
|
| R3-231207 |
Discussion on Xn impact of ES |
Samsung |
| R3-231210 |
TP to 38.423 for predicted energy saving strategy exchanging procedure for AI/ML for NG-RAN |
Samsung, Lenovo |
| R3-231377 |
AIML Energy Saving |
NEC |
| R3-231437 |
Discussion on issues related to AI based network energy saving |
Lenovo |
| R3-231466 |
Discussion on the EC metric |
CATT |
| R3-231617 |
AI-ML Network Energy Saving |
Ericsson |
| R3-231618 |
(TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving Procedures |
Ericsson |
| R3-231659 |
(TP for TS 38.423) AI/ML Energy Saving Open Aspects |
Nokia, Nokia Shanghai Bell |
| R3-231682 |
Further discussion on AIML based energy saving |
ZTE |
| R3-231801 |
Open Issues on AI ML for NG-RAN Energy Saving |
CMCC |
| R3-231812 |
Further discussion for NG-RAN AIML energy saving |
NTT DOCOMO INC. |
| R3-231826 |
(TP for AIML BLCR for TS 38.423) Remaining open issues for energy saving |
Huawei |
| R3-231881 |
CB: # AIRAN4_ES- Summary of email discussion |
Ericsson - moderator |
| R3-232028 |
CB: # AIRAN4_ES- Summary of email discussion |
Ericsson - moderator |
| R3-232092 |
(TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving Procedures |
Ericsson |
| R3-232149 |
(TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving Procedures |
Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| 12.2.2.4 |
Other interfaces |
|
| R3-231438 |
(TP for TS37.480 TS38.470) Discussion on E1 F1 interface impact |
Lenovo |
| R3-231583 |
On the Support of AI/ML over F1 and E1 interface |
China Telecom |
| 12.3 |
Others |
|
| R3-231208 |
Discussion on MDT enhancement for AI/ML for NG-RAN |
Samsung |
| R3-231261 |
Discussion on MDT enhancement for NG-RAN AI-ML |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-231355 |
Further discussions on MDT enhancements |
Huawei |
| R3-231439 |
Discussion on transferring visited cell list to old NG-RAN node |
Lenovo, ZTE, Samsung |
| R3-231604 |
Continuous MDT tracing |
Ericsson, InterDigital, Deutsche Telekom |
| R3-231605 |
(TP for AI/ML BLCR to TS38.413) Continuous MDT tracing |
Ericsson, InterDigital, Deutsche Telekom |
| R3-231606 |
(TP for AI/ML BLCR to TS38.423) Continuous MDT tracing |
Ericsson, InterDigital, Deutsche Telekom |
| R3-231607 |
LS on Continuous MDT |
Ericsson, InterDigital, Deutsche Telekom |
| R3-231660 |
MDT Data Collection Continuity for NG-RAN AI/ML |
Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-231676 |
Discussion on supporting of continues MDT |
CATT |
| R3-231842 |
Discussion on MDT enhancement for continuous AI-ML related information |
ZTE, Lenovo, Samsung |
| R3-231843 |
(TP to TS38.413) MDT Enhancements for continuous data collection |
ZTE, Lenovo, Samsung |
| R3-231844 |
[DRAFT] LS on the MDT enhancement to support continuous AI-ML related information reporting from UE |
ZTE |
| R3-231882 |
CB: # AIRAN5_MDT- Summary of email discussion |
Samsung - moderator |
| R3-232111 |
CB: # AIRAN5_MDT- Summary of email discussion |
Samsung - moderator |
| 13.1 |
General |
|
| R3-231307 |
Workplan for Rel-18 mobile IAB |
Qualcomm Inc. (Rapporteur) |
| R3-231308 |
Discusssion on issues related to SA2 VMR |
Qualcomm Inc. |
| R3-231356 |
Discussion on SA2 issues and mobile IAB authorization |
ZTE |
| R3-231482 |
Discussion on UE positioning and additional ULI for VMR |
Huawei |
| R3-231522 |
Discussion on support of MBSR |
Xiaomi |
| R3-231523 |
Support of MBSR |
Xiaomi, Ericsson, Qualcomm, CATT |
| R3-231532 |
Discussion of SA2 FS_VMR Solutions |
Ericsson |
| R3-231533 |
(draftCR TS 38.305) Introduction of MBSR |
Ericsson, Xiaomi, Qualcomm Inc., CATT |
| R3-231534 |
(CR TS 38.455) Support for MBSR Location Information |
Ericsson, Xiaomi, Qualcomm Inc., CATT |
| R3-231900 |
CB: # IAB1_General - Summary of email discussion |
Xiaomi - moderator |
| R3-232110 |
CB: # IAB1_General - Summary of email discussion |
Xiaomi - moderator |
| 13.2 |
Support IAB-node mobility |
|
| R3-231275 |
Enhancements for mobility of IAB-node together with Ues |
CATT |
| R3-231309 |
Topology adaptation for mobile IAB |
Qualcomm Inc. |
| R3-231329 |
Discussion on IAB-node DU migration |
Fujitsu |
| R3-231330 |
Discussion on IAB-node consecutive partial migrations |
Fujitsu |
| R3-231357 |
Discussion on inter-donor migration in mobile IAB scenario |
ZTE |
| R3-231440 |
Discussion on mobile IAB-node inter-donor topology adaptation |
Lenovo |
| R3-231441 |
IAB-MT and IAB-DU migrate to different IAB-donors |
Lenovo |
| R3-231470 |
Discussion on Support IAB-node mobility |
Nokia, Nokia Shanghai Bell |
| R3-231471 |
Support for mobile IAB |
Nokia, Nokia Shanghai Bell |
| R3-231479 |
Discussion on MT and DU Migrations of Mobile IAB-node |
CANON Research Centre France |
| R3-231483 |
(TP for NR_mobile_IAB BL CR for TS 38.401/38.413/38.473): Support of mobility for mobile IAB |
Huawei |
| R3-231524 |
Discussion on IAB-node mobility |
Xiaomi |
| R3-231535 |
Migration Procedure for Mobile IAB-Nodes |
Ericsson |
| R3-231717 |
Discussion on DU migration |
Samsung |
| R3-231718 |
Discussion on multiple partial migration |
Samsung |
| R3-231901 |
CB: # IAB2_IABmobility - Summary of email discussion |
Ericsson - moderator |
| R3-231955 |
(TP for NR_mobile_IAB BL CR for TS 38.413) Support of mobility for mobile IAB |
Huawei |
| 13.3 |
Mobility Enhancements |
|
| R3-231276 |
Other aspects for mobile IAB |
CATT |
| R3-231310 |
Enhancements for mobility of IAB-node and its served UEs |
Qualcomm Inc. |
| R3-231358 |
Discussion on enhancements to IAB node migration in mobile IAB scenario |
ZTE |
| R3-231442 |
Mobility enhancements for mobile IAB-node and its served UE |
Lenovo |
| R3-231472 |
Discussion on mobility enhancements |
Nokia, Nokia Shanghai Bell |
| R3-231484 |
(TP for NR_mobile_IAB BL CR for TS 38.423): Mobility enhancement for mobile IAB |
Huawei |
| R3-231525 |
Discussion on mobility enhancement |
Xiaomi |
| R3-231536 |
IAB-Node Mobility Enhancements |
Ericsson |
| R3-231719 |
Discussion on mobility enhancements |
Samsung |
| R3-231902 |
CB: # IAB3_MobEnh - Summary of email discussion |
Qualcomm - moderator |
| R3-232005 |
CB: # IAB3_MobEnh - Summary of email discussion |
Qualcomm - moderator |
| R3-232138 |
CB: # IAB3_MobEnh - Summary of email discussion |
Qualcomm - moderator |
| 13.4 |
Mitigation of interference |
|
| R3-231359 |
Discussion on PCI collision avoidance for mobile IAB |
ZTE |
| R3-231443 |
PCI collision mitigation of mobile IAB-node mobility |
Lenovo |
| R3-231473 |
Mobile IAB interference mitigation |
Nokia, Nokia Shanghai Bell |
| R3-231485 |
PCI collision for mobile IAB |
Huawei |
| R3-231526 |
Discussion on mitigation of interference |
Xiaomi |
| R3-231537 |
PCI Collision Avoidance for Mobile IAB-Nodes |
Ericsson |
| R3-231720 |
Discussion on mitigation of interference |
Samsung |
| R3-231903 |
CB: # IAB4_MitInt - Summary of email discussion |
ZTE - moderator |
| R3-232116 |
CB: # IAB4_MitInt - Summary of email discussion |
ZTE - moderator |
| 14.1 |
General |
|
| R3-231136 |
(BLCR) Additions for L1/L2 triggered mobility |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-231137 |
(BLCR to 38.401) for L1L2Mob |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| 14.2 |
Signaling Support for L1/L2 based Inter-Cell Mobility |
|
| R3-231107 |
LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
RAN1, Fujitsu, CATT |
| R3-231182 |
TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures |
Nokia, Nokia Shanghai Bell |
| R3-231183 |
Discussion on TA Acquisition for LTM |
Nokia, Nokia Shanghai Bell |
| R3-231239 |
gNB-DU initiated target cell re-configuration for L1/L2 triggered mobility |
Rakuten Symphony |
| R3-231315 |
Signalling Support for LTM |
Qualcomm Incorporated |
| R3-231326 |
[Draft] Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
Fujitsu, CATT |
| R3-231327 |
Discussion on replying to the RAN1 LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
Fujitsu, CATT |
| R3-231381 |
co-existence between LTM and L3 mobility |
NEC |
| R3-231382 |
(TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility |
NEC |
| R3-231388 |
(TP for L1L2Mob BLCR for TS 38.401) Discussion on reference configuration in LTM |
Google Inc. |
| R3-231447 |
Discussion on L1L2 based inter-cell mobility |
Lenovo |
| R3-231448 |
(TP to TS 38.401 & TS 38.470) Support of L1L2 based inter-cell mobility |
Lenovo |
| R3-231458 |
Collision between L1/L2-triggered mobility and L3 mobility |
vivo |
| R3-231459 |
Discussion on L1/L2-triggered Mobility |
vivo |
| R3-231510 |
Discussion on remaining issues for LTM procedure |
China Telecommunication |
| R3-231511 |
(TP to TS 38.473 BL CR) On support of LTM procedure |
China Telecommunication |
| R3-231573 |
(TP for LTM BL CR to TS 38.401) Solutions for LTM |
Ericsson |
| R3-231574 |
(TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
Ericsson |
| R3-231652 |
Discussion on LTM related issues |
LG Electronics Inc. |
| R3-231653 |
(TP for NR_Mob_enh2 BL CR for TS 38.401) Discussion on LTM related issues |
LG Electronics Inc. |
| R3-231654 |
(TP for NR_Mob_enh2 BL CR for TS 38.473) Discussion on LTM related issues |
LG Electronics Inc. |
| R3-231678 |
Discussion on left issues for L1/L2 mobility |
CATT |
| R3-231679 |
(TP for L1L2 Mob BLCR for TS 38.401) Support of L1L2 based
inter-cell mobility |
CATT |
| R3-231745 |
(TP for L1L2Mob BLCR for TS 38.401): L1/L2 Mobility procedure on F1 |
Huawei |
| R3-231746 |
(TP for L1L2Mob BLCR for TS 38.401): L1/L2 Mobility procedure on E1 |
Huawei |
| R3-231747 |
(TP to Mob_enh2 BL CR TS38.401) Discussion on L1/L2 based Inter-cell Mobility |
Samsung Electronics France SA |
| R3-231751 |
Considerations on parallel vs single (including TPs for TS 38.473) |
Intel Corporation |
| R3-231807 |
Discussion on L1L2 based Inter-Cell Mobility |
CMCC |
| R3-231808 |
(TP to TS 38.401) L1L2 based Inter-Cell Mobility |
CMCC |
| R3-231813 |
Further discussion on LTM |
NTT DOCOMO INC. |
| R3-231848 |
(TP for LTM BL CR to TS 38.473) Discussion on L1/L2 triggered mobility |
ZTE |
| R3-231849 |
TP for LTM BL CR to TS 38.401 |
ZTE |
| R3-231883 |
CB: # MobilityEnh1_RAN1LS- Summary of email discussion |
CATT - moderator |
| R3-231884 |
CB: # MobilityEnh2_L1L2Mobility- Summary of email discussion |
Huawei - moderator |
| R3-231937 |
CB: # MobilityEnh1_RAN1LS- Summary of email discussion |
CATT - moderator |
| R3-231938 |
CB: # MobilityEnh2_L1L2Mobility- Summary of email discussion |
Huawei - moderator |
| R3-232089 |
[Draft] Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
Fujitsu, CATT |
| R3-232090 |
(TP for L1L2Mob BLCR for TS 38.401): L1/L2 Mobility procedure on F1 |
Huawei |
| R3-232094 |
(TP for L1L2Mob BLCR for TS 38.401): L1/L2 Mobility procedure on E1 |
Huawei |
| R3-232115 |
(TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
Ericsson, Huawei |
| R3-232139 |
[Draft] Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
Fujitsu, CATT |
| R3-232145 |
(TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
Ericsson, Huawei, Lenovo, Nokia, Nokia Shanghai Bell, ZTE, Samsung |
| R3-232171 |
(TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
Ericsson, Huawei, Lenovo, Nokia, Nokia Shanghai Bell, ZTE, Samsung |
| 14.3 |
Support CHO in NR-DC |
|
| R3-231192 |
[TP to TS38423, CHO with NRDC] Avoiding unnecessary CHO replace & data forwarding in case of CHO with multiple SCGs |
Nokia, Nokia Shanghai Bell |
| R3-231235 |
(TP for CHO with NR-DC to TS 37.340): Early data forwarding optimization for CHO with SCG procedure |
ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell,Ericsson |
| R3-231236 |
(TP for CHO with NR-DC to TS 38.423): Early data forwarding optimization for CHO with SCG procedure |
ZTE |
| R3-231305 |
Discussion on avoiding CHO modification signalling in CHO with SCG(s) due to source RRC reconfiguration (including TP for TS 38.423) |
Intel Corporation |
| R3-231306 |
Discussion on the new problem of CHO with SCGs (including TP for TS 38.423) |
Intel Corporation |
| R3-231317 |
CHO with multiple candidate SCGs |
Qualcomm Incorporated |
| R3-231322 |
Discussion on CHO with SCG and multiple SCGs |
CATT |
| R3-231399 |
(TPs to TS 37.340, 38.423 BL CRs) Consideration on CHO Related aspects |
Huawei |
| R3-231449 |
(TP to TS 37.340 & TS 38.423) CHO in NR-DC |
Lenovo |
| R3-231575 |
CHO with candidate SCG(s) |
Ericsson |
| R3-231577 |
Avoid unnecessary signaling due to SCG reconfigurations |
Ericsson, ZTE, Lenovo |
| R3-231722 |
Considerations on CHO in NR-DC |
Samsung |
| R3-231885 |
CB: # MobilityEnh3_CHO- Summary of email discussion |
Ericsson - moderator |
| R3-231941 |
CB: # MobilityEnh3_CHO- Summary of email discussion |
Ericsson - moderator |
| R3-232113 |
(TP for CHO with NR-DC to TS 37.340): Early data forwarding optimization for CHO with SCG procedure |
ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, Ericsson, CATT, Samsung, Huawei |
| R3-232172 |
(TP for CHO with NR-DC to TS 37.340): Early data forwarding optimization for CHO with SCG procedure |
ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, Ericsson, CATT, Samsung, Huawei |
| 14.4 |
Others |
|
| R3-231193 |
[TP to TS 38.423 for Selective Activation] Data forwarding and RAN signalling for Selective Activation |
Nokia, Nokia Shanghai Bell |
| R3-231316 |
SCG Selective Activation in NR-DC |
Qualcomm Incorporated |
| R3-231323 |
Discussion on NR-DC with selective activation of the cell groups |
CATT |
| R3-231383 |
Selective Activation of the cell groups |
NEC |
| R3-231384 |
(TP to TS 38.423 BL CR) Selective SCG Activation |
NEC |
| R3-231400 |
(TP to TS 38.423 BL CR) Consideration on selective activation of SCGs |
Huawei |
| R3-231450 |
(TP for TS 38.473) On SCG selective activation |
Lenovo |
| R3-231460 |
Signaling Support for Selective Activation |
vivo |
| R3-231512 |
Discussion on selective activation of cell groups |
China Telecommunication |
| R3-231513 |
(TP to TS 38.423 BL CR) On support of selective activation |
China Telecommunication |
| R3-231576 |
NR-DC with Selective Activation |
Ericsson |
| R3-231721 |
Considerations on selective activation of the cell groups |
Samsung |
| R3-231816 |
Discussion on selective activation |
NTT DOCOMO INC. |
| R3-231850 |
(TP to TS 38.423 and 38.473) Support of SCG selective activation |
ZTE |
| R3-231886 |
CB: # MobilityEnh4_Others- Summary of email discussion |
ZTE - moderator |
| R3-231944 |
CB: # MobilityEnh4_Others- Summary of email discussion |
ZTE - moderator |
| R3-232063 |
(TP to TS 38.423) Support of SCG selective activation |
ZTE, Huawei |
| 15.1 |
General |
|
| R3-231153 |
Introduction of NR MBS enhancements (BL CR to 38.401) |
Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-231154 |
(BLCR to 38.300) NR_MBS-enh |
Nokia, Nokia Shanghai Bell |
| 15.2 |
Support for MBS reception in RAN sharing scenarios |
|
| R3-231187 |
Support of MBS in RAN sharing scenarios |
Qualcomm Incorporated |
| R3-231197 |
Sharing processing for both unicast reception and broadcast reception |
TD Tech, Chengdu TD Tech |
| R3-231252 |
Discussions and proposals concerning Rel-18 work on MBS reception in RAN sharing scenarios |
Ericsson |
| R3-231283 |
(TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions |
Nokia, Nokia Shanghai Bell |
| R3-231336 |
(TP for 38.473)Discussion on MBS RAN sharing |
Samsung |
| R3-231350 |
(TP for 38.413/38.473/38.401)Discussion on efficient MBS reception in RAN sharing scenario |
CATT,CBN,China Telecom |
| R3-231397 |
(TPs to TS 38.401, 38.410, 38.413, 38.473 BL CRs) MBS reception in RAN sharing scenario |
Huawei, CBN |
| R3-231445 |
Remaining issue of supporting MBS reception in RAN Sharing |
Lenovo |
| R3-231503 |
TP to TS 38.413 and 38.473 with discussion on network sharing of MBS |
ZTE |
| R3-231887 |
CB: # MBS1_NetworkSharing- Summary of email discussion |
Ericsson - moderator |
| 15.3 |
Support for RRC_INACTIVE state |
|
| R3-231188 |
Enhancements to support Multicast reception by UEs in RRC_INACTIVE state |
Qualcomm Incorporated |
| R3-231198 |
Multicast reception in RRC_INACTIVE state |
TD Tech, Chengdu TD Tech |
| R3-231199 |
Multicast reception in RRC_INACTIVE state |
TD Tech, Chengdu TD Tech |
| R3-231253 |
Discussions and proposals concerning Rel-18 work on multicast reception in RRC_INACTIVE |
Ericsson |
| R3-231284 |
(TP for TS 38.413, TS 38.423 and TS 38.300) MBS Reception in RRC inactive state |
Nokia, Nokia Shanghai Bell |
| R3-231335 |
Discussion on MBS reception by inactive state UE |
Samsung |
| R3-231379 |
MBS Inactive Reception |
NEC |
| R3-231398 |
(TPs to TS 38.300, 401, 413, 423,470, 473 BL CRs) Multicast Reception for RRC_INACTIVE state Ues |
Huawei, CBN |
| R3-231444 |
Support of multicast reception in RRC_INACTIVE |
Lenovo |
| R3-231463 |
(TP for 38.401/38.413/38.423/38.473) Discussion on multicast over RRC INACTIVE |
CATT,CBN,China Telecom |
| R3-231464 |
Proposal on how to proceed on assistant information from CN to NG-RAN node |
CATT |
| R3-231504 |
Multicast reception in RRC_INACTIVE |
ZTE |
| R3-231809 |
Multicast Reception in RRC_INACTIVE state |
CMCC |
| R3-231888 |
CB: # MBS2_RRCInactive- Summary of email discussion |
ZTE - moderator |
| R3-231975 |
(TP for TS 38.300) MBS Reception in RRC Inactive state |
Nokia, Nokia Shanghai Bell |
| R3-231981 |
(TP to TS 38.423 BL CR) Multicast Reception for RRC_INACTIVE state Ues |
Huawei, CBN |
| R3-231982 |
(TP to TS 38.470 BL CR) Multicast Reception for RRC_INACTIVE state Ues |
Huawei, Lenovo, Nokia, Nokia Shanghai Bell |
| R3-232029 |
(TP for 38.413) Introduction of multicast over RRC INACTIVE |
CATT,CBN,China Telecom |
| R3-232057 |
[TP for TS 38.401] Further text for support multicast reception in RRC_INACTIVE |
Ericsson |
| R3-232121 |
(TP for TS 38.300) MBS Reception in RRC Inactive state |
Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-232165 |
(TP to TS 38.470 BL CR) Multicast Reception for RRC_INACTIVE state Ues |
Huawei, Lenovo, Nokia, Nokia Shanghai Bell |
| 16.1 |
General |
|
| R3-231149 |
(BLCR) Support for NR Sidelink Relay Enhancements |
Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei |
| R3-231150 |
(BLCR) Support NR Sidelink Relay Enhancements |
Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCC |
| R3-231151 |
(BLCR) Support for NR Sidelink Relay Enhancements |
Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-231152 |
(BLCR to 38.401) Introduction of NR SL relay enhancements |
LG Electronics |
| 16.3 |
Support Service Continuity Enhancements |
|
| R3-231213 |
(TPs to TS 38.401 and TS 38.423) Remaining open issues on service continuity enhancement |
Samsung |
| R3-231256 |
Further discussion on service continuity for SL relay |
ZTE |
| R3-231272 |
(TP for BLCR for 38.401 and 38.423): Inter-gNB mobility |
Huawei |
| R3-231374 |
Discussion on remaining issue to support service continuity |
NEC |
| R3-231446 |
Service continuity for U2N relay |
Lenovo |
| R3-231474 |
Discussion on Support Service Continuity Enhancements |
Nokia, Nokia Shanghai Bell |
| R3-231508 |
Inter-gNB mobility for L2 U2N relay |
China Telecommunication |
| R3-231558 |
Discussion on Service Continuity Enhancements for SL relay |
CATT |
| R3-231571 |
Inter-gNB Service Continuity for L2 U2N Relay |
Ericsson |
| R3-231693 |
Support of service continuity enhancement for U2N relay |
LG Electronics |
| R3-231793 |
Service continuity for U2N relay |
CMCC |
| R3-231889 |
CB: # SLRelay1_ServiceContinuity- Summary of email discussion |
Nokia - moderator |
| R3-231942 |
CB: # SLRelay1_ServiceContinuity- Summary of email discussion |
Nokia - moderator |
| R3-231954 |
(TP for BLCR for 38.423): Inter-gNB mobility |
Huawei |
| R3-231956 |
(TP for SL relay BLCR for TS 38.401) Call flows for inter-gNB-CU switch from direct to indirect path |
LG Electronics |
| R3-231968 |
TP to TS 38.413 for inter-gNB mobility of L2 U2N relay, as guidance in CB: # SLRelay1_ServiceContinuity |
China Telecom |
| R3-231976 |
(TP for BLCR for 38.413): Inter-gNB mobility |
China Telecom |
| R3-232155 |
(TP for BLCR for 38.423): Inter-gNB mobility |
Huawei |
| 16.4 |
Multi-path Support |
|
| R3-231214 |
(TP to TS 38.401) Path addition and release for multipath for sidelink relay |
Samsung |
| R3-231257 |
Discussion on multi-path relay support |
ZTE |
| R3-231273 |
(TP for BLCR for 38.473) Multi-path relay |
Huawei |
| R3-231375 |
Discussion on remaining issue of multi-path support |
NEC |
| R3-231475 |
discussion on the support for multi-path |
Nokia, Nokia Shanghai Bell |
| R3-231507 |
On multi-path change for sidelink relay |
China Telecommunication |
| R3-231559 |
Discussion on Multi-path Support for SL relay |
CATT |
| R3-231572 |
(TP for SL Relay BL CR to TS 38.401) Multi-path for Sidelink Relay |
Ericsson |
| R3-231694 |
(TP to TS 38.401) Further consideration on multi-path support |
LG Electronics |
| R3-231794 |
(TP to TS 38.401)Considerations on multi-path for SL relay |
CMCC |
| R3-231890 |
CB: # SLRelay2_Multipath- Summary of email discussion |
LG - moderator |
| R3-231943 |
CB: # SLRelay2_Multipath- Summary of email discussion |
LG - moderator |
| R3-232088 |
(TP to TS 38.401) Path addition for multipath for sidelink relay |
Samsung, LGE |
| 17.1 |
General |
|
| R3-231139 |
XnAP BLCR on NTN Functionality |
Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| R3-231140 |
(BLCR) Stage 2 BL CR for NR NTN |
Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-231364 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| 17.2 |
Support Mobility and Service Continuity Enhancements |
|
| R3-231215 |
Remaining open issues on service continuity enhancement for NTN |
Samsung |
| R3-231255 |
Cell ID over Xn for NTN |
Qualcomm Incorporated, CATT, Nokia, Nokia Shanghai Bell, NEC |
| R3-231258 |
Discussion on NTN Service Continuity Enhancements |
Qualcomm Incorporated |
| R3-231387 |
Discussion on Mobility and Service Continuity Enhancements for NTN |
NEC |
| R3-231417 |
NGAP Support for Time-Based HO in NTN |
Ericsson, Thales, Intelsat, Lockheed Martin, Hughes Network Systems, CATT, ESA |
| R3-231418 |
Time-Based HO for NTN - NGAP Impacts |
Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, CATT, ESA |
| R3-231419 |
Time Margin for CHO in NR NTN |
Ericsson, Thales |
| R3-231420 |
Time Margin for CHO in NR NTN - XnAP Impact |
Ericsson LM |
| R3-231476 |
Discussion on the time-based trigger condition in NR NTN |
Nokia, Nokia Shanghai Bell |
| R3-231477 |
Support time-based trigger condition in NG-HO |
Nokia, Nokia Shanghai Bell |
| R3-231509 |
Remaining issues on NTN mobility enhancement |
China Telecommunication |
| R3-231669 |
Discussion Mobility and Service Continuity Enhancements for NTN |
CATT |
| R3-231684 |
Discussion on Mobility and Service Continuity Enhancements |
NEC Corporation |
| R3-231691 |
Further discussion on mobility issue for NR NTN |
ZTE |
| R3-231697 |
(TP for NTN BL CR 38.300) Cell ID for non-UE associated Xn procedures |
ZTE |
| R3-231756 |
Further discussion on cell ID usage and TAC |
Huawei |
| R3-231757 |
Further discussion on NG HO |
Huawei |
| R3-231892 |
CB: # NTN1_ServiceContinuity - Summary of email discussion |
Samsung - moderator |
| R3-232093 |
NGAP Support for Time-Based HO in NTN |
Ericsson, Thales, Intelsat, Lockheed Martin, Hughes Network Systems, CATT, ESA |
| R3-232123 |
(TP for BL CR 38.300) data forwarding in HO with time-based trigger condition |
Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R3-232159 |
NGAP Support for Time-Based HO in NTN |
Ericsson, Thales, Intelsat, Lockheed Martin, Hughes Network Systems, CATT, ESA |
| 17.3 |
Network verified UE location |
|
| R3-231328 |
Consideration on OAM requirements for UE location verification |
CATT |
| R3-231421 |
Latency Impact of Network Verified UE Location for NTN |
Ericsson, CATT, Huawei |
| R3-231453 |
OAM Requirements for UE Location Verification |
Ericsson, CATT, Huawei |
| R3-231670 |
[Draft]LS on OAM requirements for UE location verification |
CATT |
| R3-231758 |
(TP to 38.300) OAM Requirements for UE Location Verification |
Huawei, Ericsson, CATT |
| R3-231759 |
Discussion on network verified UE location |
Huawei, Ericsson, CATT |
| R3-231893 |
CB: # NTN2_LocationVerification - Summary of email discussion |
Huawei - moderator |
| 18.1 |
General |
|
| R3-231138 |
(BLCR) X2AP CR on IoT NTN Functionality |
Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-231141 |
(BLCR to 36.300) IoT NTN enhancements |
ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-231142 |
(BLCR) Support for IoT NTN enhancements |
Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| 18.2 |
Support discontinuous coverage |
|
| R3-231225 |
TP for BL CR 36.300 on NTN Handover Cell ID |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Deutsche Telekom, Verizon Wireless, NEC, Huawei, CATT |
| R3-231454 |
Time Margin for CHO in IoT NTN |
Ericsson, Inmarsat, ESA |
| R3-231455 |
Time-Based HO and IoT NTN |
Ericsson, CATT, ESA, Huawei |
| R3-231456 |
Time-Based HO for IoT NTN - S1AP Impacts |
Ericsson, Huawei, CATT, ESA |
| R3-231457 |
Which Core Network for Rel-18 IoT NTN? |
Ericsson LM |
| R3-231478 |
(TP for BL CR 36.300) on data forwarding in X2-CHO with time-based trigger condition |
Nokia, Nokia Shanghai Bell |
| R3-231597 |
(TP for BL CR 36.413 & 38.413) Further discussion on UE context release issue |
Huawei |
| R3-231677 |
Discussion on supporting discontinuous coverage |
CATT |
| R3-231692 |
Further discussion on discontinuous coverage issue for IoT NTN |
ZTE |
| R3-231894 |
CB: # IoTNTN_Coverage - Summary of email discussion |
ZTE - moderator |
| 19.1 |
General |
|
| R3-231143 |
(BLCR) Draft CR to 38.300 on NR support for UAV |
Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation, ZTE, Ericsson, Samsung, CATT, Qualcomm, Deutsche Telekom, NEC |
| R3-231144 |
(BLCR) Introduction of Aerial authorization information |
Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT |
| R3-231145 |
NR support for UAV over Xn |
Huawei, China Unicom, China Telecom, CATT, Intel Corporation, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| 20.1 |
General |
|
| R3-231155 |
Introduction of MT-SDT |
Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei |
| R3-231156 |
Introduction of MT-SDT |
Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-231157 |
(BLCR to 37.483) for MT-SDT |
Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei |
| R3-231158 |
Introduction of MT-SDT (BLCR to 38.401) |
Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom |
| 20.2 |
Support for Paging-Triggered SDT |
|
| R3-231186 |
Signaling enhancements to enable MT-SDT for RRC_INACTIVE UEs. |
Qualcomm Incorporated |
| R3-231233 |
Introduction of MT-SDT |
ZTE, China Mobile, China Telecom |
| R3-231234 |
(TP to 38.423, 38.473, 37.483) Introduction of MT-SDT |
ZTE |
| R3-231285 |
(TP for TS 38.423) Discussion on MT-SDT Open Points |
Nokia, Nokia Shanghai Bell, Orange |
| R3-231286 |
(TP for TS 37.483) Support of Paging Triggered MT-SDT |
Nokia, Nokia Shanghai Bell, Orange |
| R3-231395 |
(TPs to TS 38.300, 38.423 BL CRs) Consideration on MT-SDT |
Huawei |
| R3-231396 |
(TPs to TS 38.401, 38.473 and 37.483 BL CRs) MT-SDT in disaggregated architecture |
Huawei |
| R3-231451 |
(TP to TS 38.420) Support for Paging-Triggered SDT |
Lenovo |
| R3-231527 |
Discussion on leftover issues of MT-SDT |
Xiaomi |
| R3-231581 |
Support of MT-SDT in Split Architecture |
China Telecom |
| R3-231582 |
Discussion on MT-SDT Procedure |
China Telecom |
| R3-231639 |
Discussion on MT-SDT open issues |
Ericsson |
| R3-231640 |
(TP to TS 38.473 BL CR for MT-SDT): Support of MT-SDT Paging |
Ericsson |
| R3-231671 |
Further discussion on MT-SDT |
CATT |
| R3-231672 |
(TP for MT-SDT BL CR to TS 38 300) Support of MT-SDT |
CATT |
| R3-231695 |
(TP to TS 38.423, 38.473 and 37.483) Support of MT-SDT |
LG Electronics |
| R3-231696 |
(TP to TS 38.300 and 38.401) MT-SDT Support |
LG Electronics |
| R3-231785 |
(TP for MT-SDT BLCR to TS 38.401) UE reaction to the Paging |
Google Inc. |
| R3-231838 |
Discussion of remaining issues on MT-SDT |
Samsung |
| R3-231895 |
CB: # SDT_MTSDT - Summary of email discussion |
ZTE - moderator |
| R3-231957 |
(TP to 38.423, 38.473, 37.483) Introduction of MT-SDT |
ZTE |
| R3-231958 |
(TP for TS 38.423) Discussion on MT-SDT Open Points |
Nokia, Nokia Shanghai Bell, Orange |
| R3-231959 |
(TP to TS 38.420) Support for Paging-Triggered SDT |
Lenovo |
| R3-231960 |
(TP to TS 38.473 BL CR for MT-SDT): Support of MT-SDT Paging |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, LG Electronics, CATT, Lenovo, China Telecom |
| R3-231961 |
(TP for MT-SDT BL CR to TS 38 300) Support of MT-SDT |
CATT |
| R3-231994 |
(TP to TS 38.401 BL CR) MT-SDT in disaggregated architecture |
Huawei |
| R3-232086 |
(TP for BLCR to 37.483) Introduction on MT-SDT |
ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Xiaomi, Ericsson, LG Electronics, Lenovo |
| R3-232087 |
(TP for TS 38.423) Discussion on MT-SDT Open Points |
Nokia, Nokia Shanghai Bell, Orange, ZTE, CATT, Lenovo, Ericsson |
| R3-232108 |
(TP for MT-SDT BL CR to TS 38 300) Support of MT-SDT |
CATT, Ericsson, ZTE, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, China Telecom, Huawei, Google |
| R3-232114 |
(TP to TS 38.420) Support for Paging-Triggered SDT |
Lenovo, CATT, ZTE |
| R3-232124 |
(TP to TS 38.401 BL CR) MT-SDT in disaggregated architecture |
Huawei, ZTE, Nokia, Nokia Shanghai Bell, Google, LG Electronics, CATT, Lenovo, Ericsson |
| 21.1 |
General |
|
| R3-231641 |
WI work plan for Rel-18 RedCap |
Ericsson (Rapporteur) |
| 21.2 |
Support Enhanced eDRX in RRC_INACTIVE |
|
| R3-231103 |
LS on Paging Policy Information for Network Triggered Connection Resume |
CT4, Ericsson |
| R3-231113 |
LS on INACTIVE eDRX above 10.24sec and SDT |
RAN2, Intel |
| R3-231237 |
Introduction on NR Redcap enhancement |
ZTE |
| R3-231238 |
(TP to 38.413, 38.423) Introduction on NR Redcap enhancement |
ZTE |
| R3-231262 |
Discussion on RRC Inactive with long eDRX Support for RedCap |
Qualcomm Incorporated |
| R3-231263 |
Redcap |
Qualcomm Incorporated |
| R3-231287 |
Support of Extended eDRX in RRC Inactive |
Nokia, Nokia Shanghai Bell |
| R3-231288 |
Support of Extended DRX in RRC_INACTIVE |
Nokia, Nokia Shanghai Bell |
| R3-231303 |
Discussions for RAN2 LS on INACTIVE eDRX > 10.24s and SDT, and its impacts on Rel-17/18 SDT framework in RAN3 |
Intel Corporation |
| R3-231304 |
[Draft] Reply LS on INACTIVE eDRX above 10.24sec and SDT |
Intel Corporation |
| R3-231530 |
Discussion on RAN2 LS on INACTIVE eDRX above 10.24sec and SDT |
Xiaomi |
| R3-231531 |
(TP to TS 38.413) Support of long eDRX above 10.24 sec and SDT together |
Xiaomi |
| R3-231562 |
Discussion on long eDRX for RRC_INACTIVE base on SA2 progress |
CATT |
| R3-231563 |
Discussion on long eDRX for RRC_INACTIVE base on CT4 and RAN2 progress |
CATT |
| R3-231642 |
Discussion on RAN3 enhancements to support CN MT communication handling for RRC_INACTIVE eDRX beyond 10.24 sec and other topics |
Ericsson |
| R3-231643 |
Draft BL CRs to TSes 38.413, 38.410, 38.300, 38.423, 38.473 for eRedCap support |
Ericsson |
| R3-231765 |
Discussion on long eDRX support for RRC_INACTIVE |
Huawei |
| R3-231766 |
NGAP CR on RedCap enhancement |
Huawei, CMCC, China Unicom |
| R3-231767 |
Discussion on R18 RedCap capability |
Huawei |
| R3-231896 |
CB: # Redcap_eDRX - Summary of email discussion |
Ericsson - moderator |
| R3-231948 |
CB: # Redcap_eDRX - Summary of email discussion |
Ericsson - moderator |
| R3-231949 |
introduction of MT Communication Handling Request and DL Data Notification |
Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Qualcomm Inc., CATT, LGE |
| R3-231950 |
introduction of MT Communication Handling Request and DL Data Notification |
Nokia, Nokia Shanghai Bell |
| R3-231951 |
RAN3 progress on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 |
Ericsson |
| R3-231962 |
(TP to 38.423) Introduction on NR Redcap enhancement |
ZTE |
| R3-231963 |
(TP to 38.473) Introduction on NR Redcap enhancement |
Huawei |
| R3-231964 |
(TP to 38.300) Introduction on NR Redcap enhancement |
CATT |
| R3-232126 |
introduction of MT Communication Handling Request and DL Data Notification |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Incorporated |
| 22.1 |
General |
|
| R3-231146 |
(BLCR) 38300 BL CR for Network Controlled Repeater management |
ZTE, China Telecom, Samsung,CATT, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-231147 |
(BLCR) Support of Network-Controlled Repeater |
Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson, Samsung, NEC, China Telecom, ZTE |
| R3-231148 |
(BLCR) Support of Network-Controlled Repeater |
Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Samsung, China Telecom, ZTE, NEC |
| R3-231905 |
(BLCR) Network-Controlled Repeaters Authorization |
Ericsson, CATT, Nokia, Nokia Shanghai Bell |
| R3-231908 |
(BLCR) Network-Controlled Repeaters Authorization |
Ericsson, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| 23.1 |
General |
|
| R3-231673 |
Work Plan for Rel-18 WI on Expanded and Improved NR Positioning |
CATT, Intel Corporation, Ericsson |
| 23.2 |
Support Enhancements on NR Positioning |
|
| R3-231106 |
LS Reply on PRU Procedures |
RAN1, Qualcomm |
| R3-231116 |
LS on SRS configuration request |
RAN2, Huawei |
| R3-231218 |
Initial discussion on SL positioning |
Samsung |
| R3-231219 |
Initial discussion on enhancements for enabling LPHAP |
Samsung |
| R3-231279 |
Enhancements for LPHAP |
Qualcomm Incorporated |
| R3-231280 |
Integrity of NR Positioning Technologies |
Qualcomm Incorporated |
| R3-231312 |
RAN3 impacts of Rel-18 accuracy enhancements |
Nokia, Nokia Shanghai Bell |
| R3-231313 |
RAN3 impacts of Rel-18 sidelink positioning |
Nokia, Nokia Shanghi Bell |
| R3-231528 |
Discussion on positioning enhancement |
Xiaomi |
| R3-231529 |
(TP to 38.413) support of sidelink positioning and ranging service authorizations |
Xiaomi |
| R3-231598 |
Discussion on LPHAP |
Huawei |
| R3-231599 |
Draft Reply LS on SRS Configuration Request |
Huawei |
| R3-231600 |
Discussion on Sidelink |
Huawei |
| R3-231644 |
Discussion on RAN3 impacts to support Rel-18 positioning enhancements |
Ericsson |
| R3-231645 |
Draft BL CRs to TSes 38.455, 38.473, 38.413, 38.423 for NR Positioning Enhancements support |
Ericsson |
| R3-231674 |
Considerations on Expanded and Improved NR Positioning |
CATT |
| R3-231675 |
(TP for BLCRs) Consideration on Expanded and Improved NR Positioning |
CATT |
| R3-231810 |
Initial Consideration on NR SL Positioning |
CMCC |
| R3-231832 |
Discussion on solution of LPHAP |
vivo |
| R3-231839 |
Discussion on sidelink positioning and intergrity |
ZTE |
| R3-231840 |
Discussion on LPHAP impacts |
ZTE |
| R3-231904 |
CB: # Positioning_Enh - Summary of email discussion |
Huawei - moderator |
| R3-231952 |
Draft Reply LS on SRS Configuration Request |
Huawei |
| R3-231953 |
Positioning EnhancementOverall Open issues and Way Forward |
Huawei |
| R3-232036 |
Draft Reply LS on SRS Configuration Request |
Huawei |
| R3-232037 |
Positioning EnhancementOverall Open issues and Way Forward |
Huawei |
| R3-232038 |
(TP for the BL CR 38.413) SL Pos Authorization NGAP |
Huawei |
| R3-232039 |
(TP for the BL CR 38.423) SL Pos Authorization Xn |
Huawei |
| R3-232040 |
(TP for the BL CR 38.473) SL Pos Authorization F1AP |
Huawei |
| R3-232041 |
[Draft] LS on NTN User Location Report at UE context Release |
Huawei |
| R3-232119 |
CB: # Positioning_Enh - Summary of email discussion |
Huawei - moderator |
| 24.1 |
General |
|
| R3-231122 |
LS on 3GPP work on Energy Efficiency |
SA5, Huawei |
| R3-231415 |
WI Work plan for R18 network energy savings |
Huawei |
| 24.2 |
Support Network Energy Savings |
|
| R3-231211 |
Discussion on network energy saving |
Samsung |
| R3-231212 |
CR to 38.473 for paging enhancements on NES |
Samsung |
| R3-231266 |
Introduction of Network Energy Saving |
Ericsson |
| R3-231277 |
(TP for BLCR) Discussion on Inter-node Beam Activation |
CATT |
| R3-231278 |
(TP for BLCR) Discussion on Paging Enhancement |
CATT |
| R3-231297 |
(TP for NES WI for 38.473) Considerations on network energy savings |
Intel Corporation |
| R3-231298 |
Baseline CR to 38.423 on NES |
Intel Corporation |
| R3-231348 |
Paging enhancements and Inter-node beam activation |
Qualcomm Incorporated |
| R3-231407 |
Introduction of Network Energy Saving |
Ericsson |
| R3-231416 |
(TP to TS 38.473, 38.413 and 38.470) Network energy saving techniques |
Huawei |
| R3-231494 |
Network energy saving techniques |
Huawei |
| R3-231540 |
Baseline CR to 38.423 on NES |
Intel Corporation |
| R3-231595 |
Discussion on NES related issues |
Lenovo |
| R3-231630 |
Discussion on network energy saving techniques |
Nokia, Nokia Shanghai Bell |
| R3-231631 |
Introduction of Network Energy Saving |
Nokia, Nokia Shanghai Bell |
| R3-231781 |
(TP to BL CR of 38.473) Paging enhancement |
ZTE |
| R3-231782 |
(TPs to BL CRs of 38.423_38.473_38.300) Inter-node beam activation |
ZTE |
| R3-231897 |
CB: # NetworkES_Solutions - Summary of email discussion |
Huawei - moderator |
| R3-231983 |
Introduction of Network Energy Saving |
Ericsson |
| R3-231984 |
Network energy saving techniques |
Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Samsung, CATT |
| R3-231985 |
LS on the enhancements on restricting paging in a limited area |
Huawei |
| R3-232052 |
BL CR of 38.300 on Network energy saving techniques |
ZTE |
| R3-232082 |
Introduction of Network Energy Saving |
Ericsson, Huawei, Samsung, ZTE, CATT, Intel |
| R3-232083 |
Network energy saving techniques |
Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel |
| R3-232084 |
LS on the enhancements on restricting paging in a limited area |
Huawei |
| R3-232085 |
(BL CR for TS38.300) Network energy saving techniques |
ZTE |
| 26.1 |
eNPN WI |
|
| R3-231250 |
Introduction of equivalent SNPNs |
Ericsson |
| R3-231254 |
Introduction of Rel-18 eNPN work in RAN3 specifications |
Ericsson |
| R3-231289 |
Support of Further Enhancements of NPN for NG-RAN |
Nokia, Nokia Shanghai Bell |
| R3-231290 |
Introduction of Further Enhancements of NPN for NG-RAN |
Nokia, Nokia Shanghai Bell |
| R3-231338 |
Discussion on Enhanced support of NPN |
Samsung |
| R3-231349 |
Equivalent SNPNs and non-3GPP access for SNPN |
Qualcomm Technologies Int |
| R3-231385 |
introduction of eNPN |
NEC |
| R3-231386 |
Support for non-3GPP access for SNPN (CR to 29.413) |
NEC |
| R3-231410 |
(TP to TS 38.423, 38.300 and 29.413) Support of the enhanced NPN phase 2 |
Huawei |
| R3-231411 |
Support of the enhanced NPN phase 2 |
Huawei |
| R3-231506 |
On introduction of R18 eNPN |
China Telecom, Huawei, ZTE, CATT |
| R3-231516 |
Work Plan for eNPN_Ph2-NGRAN WI |
China Telecommunication |
| R3-231517 |
Discussion on Xn/NG enhancement to support eNPN |
China Telecommunication |
| R3-231716 |
Addition for Rel-18 eNPN |
Samsung |
| R3-231772 |
(TPs to BL CRs of 38.423_38.413_38.300) for eNPN phase 2 |
ZTE |
| R3-231773 |
Discussion on RAN support for eNPN phase 2 |
ZTE |
| R3-231814 |
Discussion on RAN impact for NPN enhancement in Rel-18 |
CATT |
| R3-231815 |
[TP to 38413 and 38423 to NPN] Discussion on RAN imapct for NPN enhancement in Rel-18 |
CATT |
| R3-231817 |
Consideration on RAN impact of eNPN Phase 2 |
LG Electronics |
| R3-231898 |
CB: # NPN_RANenh - Summary of email discussion |
China Telecom - moderator |
| R3-231967 |
CB: # NPN_RANenh - Summary of email discussion |
China Telecom - moderator |
| R3-231977 |
Introduction of equivalent SNPNs |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| R3-231978 |
On introduction of R18 eNPN |
China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson |
| R3-231979 |
(BL CR) Support of the enhanced NPN phase 2 |
ZTE |
| R3-231980 |
Support of the enhanced NPN phase 2 |
Huawei, China Telecom, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, ZTE, Samsung, Ericsson |
| 26.2 |
Timing Resiliency and URLLC WI |
|
| R3-231115 |
Reply LS on Proposed method for Time Synchronization status reporting to UE(s) |
RAN2, Nokia |
| R3-231194 |
Work plan for Timing Resiliency and URLLC enhancements |
Nokia (rapporteur) |
| R3-231195 |
(TP for TS 38.413 BL CR) 5GS network timing synchronization status and reporting |
Nokia, Nokia Shanghai Bell |
| R3-231196 |
(TP for TS 38.413 BL CR) RAN feedback for low latency communication |
Nokia, Nokia Shanghai Bell |
| R3-231264 |
Discussion on Time Synchronisation Status and Reporting |
Qualcomm Incorporated |
| R3-231265 |
Discussion on Adaptive UL and DL Scheduling |
Qualcomm Incorporated |
| R3-231274 |
Discussion on NR Timing Resiliency and URLLC enhancements |
Ericsson |
| R3-231324 |
Discussion on Network timing synchronization status and reporting |
CATT |
| R3-231325 |
Discussion on Adapting downstream and upstream scheduling |
CATT |
| R3-231409 |
Support NR Timing Resiliency and URLLC enhancements |
Ericsson |
| R3-231412 |
(TP to TS 38.423 and 38.473) Support of Timing Resiliency and URLLC |
Huawei, China Unicom |
| R3-231413 |
Support of Timing Resiliency and URLLC |
Huawei, China Unicom |
| R3-231661 |
Discussion on network timing synchronization status and reporting |
Samsung |
| R3-231662 |
Discussion on adapting downstream and upstream scheduling based on RAN feedback |
Samsung |
| R3-231783 |
Discussion on timing synchronization status and reporting |
ZTE |
| R3-231784 |
Discussion on RAN feedback for downstream scheduling |
ZTE |
| R3-231811 |
Discussion on RAN3 Impact of Timing Resiliency and URLLC Enhancements |
China Telecom |
| R3-231899 |
CB: # URLLC_RANenh - Summary of email discussion |
Nokia - moderator |
| R3-231939 |
(TP for TS 38.413 BL CR) 5GS network timing synchronization status and reporting |
Nokia, Nokia Shanghai Bell, CATT, Huawei |
| R3-231940 |
(TP for TS 38.413 BL CR) RAN feedback for low latency communication |
Nokia, Nokia Shanghai Bell, CATT, Huawei |
| R3-231969 |
(TP for TS 38.413 BL CR) 5GS network timing synchronization status and reporting |
Nokia, Nokia Shanghai Bell, CATT, Huawei, ZTE, Samsung, Ericsson |
| R3-231970 |
(TP for TS 38.413 BL CR) RAN feedback for low latency communication |
Nokia, Nokia Shanghai Bell, CATT, Huawei, Qualcomm Incorporated |
| R3-231971 |
CB: # URLLC_RANenh - Summary of email discussion |
Nokia - moderator |
| R3-231989 |
Support of Timing Resiliency and URLLC |
Huawei, Nokia, Nokia Shanghai Bell |
| R3-231998 |
(BL CR for TS 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements |
Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT |
| R3-232066 |
(BL CR) Support NR Timing Resiliency and URLLC enhancements |
Ericsson |
| R3-232109 |
(BL CR for TS 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements |
ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-232152 |
(BL CR for TS 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements |
Ericsson |